Anyone has experience extend "Item Description" (tc.dsca)?
I need to know any effect to other object. And do we need to
modify all of them.

Thanks in advance.

Hej,

did I understand you correctly, that you would like to change the domain length of for the item description? Domain tcdsca?

I would not recommend that, since this domain is used at extremly many places.

Hello, I think that when you change tcdsca properties , this causes chaging all of item properties that used it. I think that you must examine your system data properties. According to its usage may be it won't affect the system . You can use maintain domain for your resourcing. In my opinion , you should create your domain , don't customize standart domain of BAAN ...

Good luck!

Hej,

i totally agree with Mr Suleyman, only customize domains if there is absolutly no other way.

Even Creating your own customized domain for tcdsca will be a problem because you will still have to go and change the domain in all the reports that will be using the Item Description.

Since you have to do the dirty work anyway, the best thing is to do a where used domain and list out the number of reports/forms that you have. That way you can go ahead and create a new domain and link it to whereever it is applicable.

Maxime.

Hi,

Thaks for all your recommend. Actually I tried to extend its length from 30 to 50 (jus t for testing in separeted VRC) and test some reports without modify any program or recompile. I found most of reports and forms look ok. But I'm not sure is there any object get effect. Just to share with you.
Many Thanks.

An approach that I have seen work with out to much trouble is to leave the domain and table alone but add a new table with item/cntr key and a description field with a new domain. (60 char in my experience). The item maintenace program needs a small mod to maintain the new table and the existing field. (The existing 'dsca' field was the same as the first 'dsca' (30) characters of the new field.)

I think you will find that the 'dsca' field is already truncated on many reports. This leads me to the proposition that the long field will not be absolutely necessary on all reports where description is printed / displayed.
Therefore it will be necessary to change only a few programs where the long description is really necessary. (This assumes that the description will be entered in a sensible manner (NATO coding would be fine)

Using this approach you can minimise the extent of customisation required and provide the long description where ever it is really required. This will ease the pain of version upgrade in the future.

Terry

Hej,

Baan told me once that if you modify a domain or a label, all form-objects will be copied into your customisation VRC when you run the next Create Runtime Data Dictionary for Forms and Menus.

Have a look at the objects in your system (Display Dumps by Form "ttadv3538m000").