Is it possible to create DD for just one table?
After installing a solution, sometimes a table won't take effect of changes made. So I have to "create DD" for that table, because "Convert to runtime" doesn't work.
But I don't want the whole package VRC to be "created".
How can I make this?

You can use session "Create Runtime Data Dictionary" (ttadv5210m000).

I've been trying to create DD for that table, but changes are not shown after the process is finished. I'm not able to wee the new fields of the table. I've created sequential dump of the table, deleted the table and re-created de table. Still nothing...

I'm out of ideas now!

Have you tried do restart shared "baan memory" service, sometimes, when you have "table def in shared memory" you have to do this before new table definitions are loaded. If it does´nt work try reboot...

Hope it would help.

J.Santana

What is your OS (and Baan version/PMC I or II - new version)? On NT, you may need to refresh you shared memory (as mentioned).

Have you checked your RTDD at OS level to see what is going on there? Also, a create without the reorganization of the table will not work since Baan will not swap the .new with the corresponding DD of the table. You may also need to update your domains.

Be sure you are in the correct PC to view the changes

[I suppose your table is, eg, tfacp999], do the following:

(connected to correct package combination)
- check you can see the new DD of the table from maintain tables
IF you don't see it, then it's obvious!

- check that the VRC where it is located can be seen by your current package combination (check your VRC/PC structure)
Your package combination may be useing VRC's that are not on top of the VRC where the table DD is, thus will never be seen!

- check that it's correct at RTDD level (check your files dict/dd<package_combination>/dtfacp/*acp999*)
IF you have a .new file, then the CRTDD did not work, you still need to convert RTDD first before the CRTDD.
IF you don't see the new fields, then your CRTDD did not updated it, check previous steps.
IF all it's ok, then restart shared memory.

One of these steps should show you where the problem is.

Did you also create runtime for any changed domains? Otherwise the table won't reconfigure. Be aware that domains can be of a different package!

Greetz,

Marc

When I stopped shader memory, the chages took effect.

Thanks.