Hallo, very strange problem.
I have a custom table, today i decide to add a field, then i convert to runtime, exit and re login and when i run the maintain session i receive error 512 ( corrupted dd), so i verify the dict(no *.new is present), i verify the oracle table structure and it has the new field.
I try to enter with ttaad4100, and with this i can see the table and the new filed.
The table is not in shared memory.
The table has no relations with other table.

Can someone have any idea?
Thanks
Barbara

Take a look at the domains used by the fields in the table and compare Baan vs. Oracle.

Everything is the same in Oracle and Baan, table, domain and filed.
Thanks
Barbara

Are you shure all VRCs are correct converted?
Is it possible to enter/change data with ttaad4100?

Regards
csecgn

Yes with ttaad4100 i can enter and modify data.
And table ttadv501,502,503,504 are empty.

Thanks
Barbara

Just a thought - but is the program in shared memory? Have you tried a CRDD on the session itself?

i have nothing loaded in shared memory
I try now the CRDD of my session but is the same
Thanks

The only other thing I can think of is something our admin has done before -I think he has forced a rebuild on the table - I am not sure what he used but I think is was bdbreconfig.

What I have done before is - make a change to something like a label and do then re-create RDD. No promise this will work - just a thought.

One other thought, it seems like, if you can edit in ttaad4100, that the table IS converted in the database, and Baan DOES see it. It may be a problem with viewing / VRCs.

If you make a change in VRC A, while logged into a company attached to VRC A, and can view this in GTM and change it, then the table change worked. Please be sure at this step, though, that the company you are running (the company shown on your main Baan Menu) in is the SAME as the company you are checking in ttaad4100. If it is NOT, this may explain your problem.

Because, how are you running the session then. If you exit and run the session under a different company attached to a different VRC, you would get this error.

Just a guess. Maybe provide more info on what VRC's the table has been changed in, Companies you are checking, and User Login Companies are in play here.