>I created some test directories yesterday for my data and copied all the tables and the DBC from the original to the new directory. One of the tables refuses to recognize it's part of the new directory and insists it's part of the old location (i.e. the table file location remains in the original directory and I get other errors to the effect the table doesn't belong to the DBC). I have tried removing it from the DBC in the current directory, freeing it from the DBC in the other directory, then copying the table and adding it back to the current DBC.



The DBC stores the location of the tables it contains.If the tables are in the same directory or a sub-directory of the DBC's directory then the DBC stores the relative path to the table(s).

The DBC is itself a table ; examine how the DBC points to the table in contains by issuing a USE on the DBC.

I place all contained tables in the same directory as the DBC or in a subdirectory of the directory holding the DBC. Then I copy the database,the tables and the sub-directory structure of the contained tables with no problems.
The only thing you have to worry about then is whether or not the database is included in the project .... this would generate a messagebox when you open up a project with a database that has been moved.

HTH ,
Dave.