>>>This is a database of 379 tables, 212 views, 96 relations - impossible to work this in MODI DATA .
>>
>>Are there any backups? Even if old, can you rename the production DBC, overwrite with the backup, and REINDEX or similar?
>>
>>ISTR there used to be GenDBC/GenDBCX tools which you could run against a backup, might help with restoring your production one.
>
>The output of GENDBC simply REPLACES the info in the DBC.RIINFO with the DBC opened as a table. The code is faulty, I would not trust something like
>
>LOCATE FOR ObjectType = 'Relation' AND 'ident_ku'$Property AND 'kunden'$Property AND 'ident_ku'$Property AND ParentID = nObjectID
>
>because
$ might catch the wrong part of Property and so on. This is to easy to create havoc.
>At least it is an idea.
I'm still on VALIDATA DATA without VALIDATE DATA, because it needs manual action. I just like to know if and what is dead.
While doing that, I solved the riddle of Code in 60dbcpro.frx. Property of the field holds a string. Somewhere in the string is a byte with the value of Code, followed with the information, followed with character 00. Some of those values are optional, so they do not occur when no value is set. Using this, the code from above should be:
LOCATE FOR;
ObjectType = 'Relation' AND ;
0h0D+'ident_ku'+0h00$Property AND ;
0h12+'kunden'+0h00$Property AND ;
0h13+'ident_ku'+0h00$Property AND;
ParentID = nObjectID
Do we have GendDBX somewhere ? The link on FoxWiki is dead.
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord
Weeks of programming can save you hours of planning.
OffThere is no place like [::1]