Sounds like the backlink in one or more of the tables may be stored as an absolute path rather than a relative path. Backlinks are normally stored as relative paths, and are therefore valid as long as the location of the DBF's relative to the DBC remains the same. This enables you to move the entire database (DBC and DBF's) as a group without getting backlink errors.

You can check for absolute backlinks in your tables by opening them with a hex editor and looking at the link in the table header. If the backlink is an absolute path you can change it to a relative path with the editor. This is risky but not difficult. Be sure that you don't change the length of the header, and MAKE A BACKUP FIRST. I have successfully fixed a couple of table headers this way.

Ordinarily you would run VALIDATE DATABASE RECOVER to fix broken backlinks, but this only works from the command window and not within a program.

>Sometimes my users copy tables and dbcs files between
>directories and got
>"Cannot resolve backlink error"
>
>Is it possible to remove programmatically backlink without third-party utility in exe file ?