Hi all,

I'm face "Error 512" on some table I have (after I did

convert runtime DD and tried to return back

to the old deffinitiion)... Error 512 means a corrupted

DD for this table.

Is this a way to recover the contents of this table?

Thanks.

All I can suggest is a create to runtime wide open. Perhaps a reference from another table has you messed up? Those are hard to get around sometimes, and you have to smack the system around. Before the create, try renaming the table a little, so there is a 'change flag' out there for it, and it is specifically picked up again during the create.

What database are you using, and do you have tools to back up the table from there?

which database ur using ?

I have seen error 512 in folllowing cases.

1. I make some change to table design and if I try to access the table until I reconfigure the tables (log out/log in) , I get the error 512 on that table.

2. I try to access the table of company with package combination other than current one which has slight modification in table definition for the table being accessed.

Muheeb

Why do you want to revert to the old RDD again?

If your table already is reorganized, then the new datastructure is in the database already. Changing the RDD will not change the datastructure.

tools tables --> RDD --> datastructure in DBMS
__1______ --> _2__ --> __3_________

1) Via solution from Baan or own modifications tools tables (tabeldefinitions) can get altered
1-2) Now a new Runtime Data Dictionary (Runtime version of Tools Tables) must be made, to allow fast access.
2) The RDD info contains domain and table structure data, but only the description of the data
2-3) This new datastructure must be applied to the database itself which is done by an export with the old runtime data dictionary followed by the import with the new datadictionary
3) Once the datastructure is in the DBMS, the system still needs the RDD to access the data. When the RDD and the datastructure in DBMS mismatch, then error 512 is given.

There are 2 points in time where 512 can happen:
after the 1-2 step, before 2-3 and when the old 2 is put back after the 2-3 step.