Correct. I expect to have to use SetLogonInfo() and/or SetTableLocation() methods in CRASDRT.DLL to handle this. Table names won't change, but the location of the .DBC and DBFs will vary on the target machines. At this point I'm not sure if I'll need one or both of these methods to reset dbc/dbf locations at runtime. Using ODBC, I simply changed the database path in the ODBC DSN programmatically at runtime via the API.

Any suggestions?

Jeff