>This problem just started on a few of our developer's PCs and we've been unable to track it down.
>
>I build and test an application on my hard drive (c:\) and everything is OK. I then copy the EXE to the Network to test with the live system.
>PROBLEM: The DBC is referencing tables on my hard drive or it's using the DBC from my hard drive NOT the Network. If I rename the folder on my hard drive and rerun the EXE it works properly. We tried compiling the same code on another PC and it works OK.
>
>I've checked all my paths and I'm not referencing the hard drive anywhere! It's as though there is code that says:
>
>If c:\vfpapp exists
> use c:\vfpapp\vfpapp.dbc
>else
> use vfpapp.dbc (current folder)
>endif
>
>But I know there is no such code like this.
>
>Any ideas?
If a .DBC's tables are
not in the same folder as the .DBC, it stores a path to the tables so it can find them. This path may include a drive letter.
If that's what's happened in your case, even though the .DBC is on a new drive it is still pointing to tables on your local drive.
This problem can be avoided by having the tables in the same folder as the .DBC.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up