Hi,

I've created a label in tdB40O_c4_liv0 called tdsls040.eono

I am trying to put this label onto the tdsls440301000 report which is in the same VRC. But when I try to enter the label on to my report it keeps on resorting to using tdsls050.eono.

I am entering the correct label length and in the "Maintain Report Label Fields" ttadv3143s000 even when I zoom to my label it keeps on trying to use tdsls050.eono.

Whats going wrong?

Thanks

PJ

Is the label in "td" package? I am quoting something that I wrote in a different forum a long while back.
Labels in Baan cannot be used across packages. You may see a label like tccom001.emno that seems to work in all packages. But look closer ... the label is

package label
tc tccom001.emno
td tccom001.emno
ti tccom001.emno


Infact there is a session (ttadv1240m000) to copy labels from one package to another. And this is what Baan does during development. And changes to the definition of such a label in one package does not propagate to other packages.

~Vasmi,

My label details are: -

Language = 2
Package = td
label = tdsls040.eono

Thanks

PJ

PJ,

From yours and ~Vamsi post it reminded me of a problem I once had. When entering the label in ttadv3143s000 are you entering tdsls040.eono or are you entering td tdsls040.eono? The second is usually correct. I created labels for one of my tables once and it took me a while to figure out that when I created the lables I did tu tuddc905.site.

Mark

Mark,

I tried your suggestion and yes it didn't change to tdsls050.eono. The only thing is it didn't bring the label text up. Where the text normally appears the box remains blank and it doesn't allow me to type my own description in?????

Philip

I can think of two possible problems:
1) the label you supplied doesn't exist (try zooming to make sure the label is exact), or
2) the size of the label you are trying to use is too big for the place you are trying to put it (try increasing the size of the place you are putting it. Again, you can zoom to see the size(s) defined in hte database).

Good luck!

I think it has to do something with the label search algorithm...

iadv0037.search.label
domain ttadv.clab iadv0037.search.label( domain ttaad.clan clan.p, domain ttadv.cpac cpac.p, domain ttadv.clab clab.p fixed, ref long leng.p, ref long lhgt.p, domain ttadv.vers vers.p, domain ttadv.rele rele.p, domain ttadv.cust cust.p, ref domain ttcdes desc.p mb, long search.by.relation, [ long dynamic ], [ domain ttadv.cont cont.p ] )


desc:
retrieves label description and puts it in desc.p
if context group is specified, index 4 is used to retrieve label,
else index 1 is used.
pre:

post:

in:
clan.p = language code
cpac.p = package code
clab.p = label code
vers.p = version code
rele.p = release code
cust.p = customer code
search.by.relatioon = ?
dynamic = [optional] if true and no label found in ttadv140 for label with
length <= leng.p, search continues for label with length between leng.p and
maximum label length (70).
cont.p = [optional] context group
out:
leng.p = length of retrieved label
lhgt.p = height of retrieved label
desc.p = label description
ret:

Hello,

Ed- The label does exist and yes I can zoom to it. I have also verified the size of the label and there is room on the layout where I'm trying to place it.

NPRao2000 - You've lost me in the wilderness..........


Thanks for your replies.


PJ

Maybe you can post screen prints of the zoom to Maintain Labels and the form label entry sessions. It might help.

Screen prints as requested

PJ

I looked at your screen prints. And "YES" you should be able to type in "tdsls040.eono" in the label field and have it return the label. OR you could zoom to the label and select it. Either way it should be working. I wonder if there could be something wrong with the table and its indexes? Maybe that is why it returns tdsls050.eono when you type in tdsls040.eono.

We saw something like this with our indexes for BOM records not too long ago. When you tried to delete a BOM component, it would tell you that it could not delete it - it had problems with the component warehouse table. I can not remember the exact error. We had to rebuild all of the indexes on the BOM tables before we could delete records. I may be totally off base with this, but I do not see where you are doing anything wrong. Do other labels with tdsls040 work? What about the tdsls050 labels - do they work if you select them?

Sorry about the guessing, but maybe it will help someone actually solve the problem.

Mark

Mark,

I can put other tdsls040 labels and also tdsls050 labels on to my report.

Cheers

Philip

I saw something a while back that rang a bell, so I tried something out.

In your table definition for tdsls040, do you use your tdsls040.eono label, the tdsls050.eono label, or did you type something in? It looks the default label is tdsls050.eono. This seems to cause the label to "switch" from tdsls040.eono to tdsls050.eono when you enter it on a form/report. I'm then guessing that your second effort was typing "tdtdsls040.eono" in the label field in ttadv3143s000 (Maintain Report Label Fields). This didn't switch because it was, in fact, using tdtdtdsls040.eono, which doesn't exist -- hence the blank field.

I did a test. I changed the related label on the tdsls040 table to tdsls040.eono (from tdsls050.eono). When I went back to add my label on the report (after DD conversion) and typed in tdsls040.eono, it worked. Somehow the label relation on the table must overshadow the fact that you have created a label whose name happens to correspond with the default Baan label name for that table field.

So, it looks like you can either change the table definition of tdsls040 or change you label name to something like tdsls040.eono.1.

I hope this helps.

Cheers Ed,

I changed the label to tdsls040.eono.1 and this worked.

Thanks for all your efforts guys.

Have Good Weekends!

PJ

Hi PJohn,

I guess I was too cryptic...

well I checked the tools documentation and found that function.

I guess if 2 labels are of the similar description/content, then the label with longer length is returned by that function.

Also, with the new BaaN releases a new field is added to the index called the "label context".