SNIP

>Thanks for replying. Unfortunately I've left the code in the office. I do have something new for you, however. This is how we are set up: We have a test web server we call Web0 (WinNT 4.0 Server). Our VFP data is on a different machine (WinNT 4.0 Workstation). Our development environment is still another machine (WinNT 4.0 Workstation). Our web server, Web0 and the DSN we created, sees the data as mapped to H:\WEBMIPS\DATA\MIPSDATA.DBC. Our development environment sees the data mapped to K:\WEBMIPS\DATA\MIPSDATA.DBC (The H: drive is not used because it had previously been mapped to a legacy application in our Marketing department that hard codes to their server's H: drive. Are you following? Using Visual InterDev 6 (the release we got at the Orlando VFP DevCon), I took a look at the properties of the data environment. It is seeing the MIPSDATA.DBC mapped to K:\WEBMIPS\MIPSDATA.DBC (the same as our development environment). Shouldn't it see the data from the point of view of
>the web server? What gives? Any ideas?
>
>Thanks,
>
>Dan Rhymes

InterDev does not see the data from the server's point of view. The InterDev client uses the DSN that's set up on it's machine. The web server uses the DSN that's set up on it's machine (Web0). That's why the mappings are different. If you ever move the data, you have to change BOTH DSNs. IMHO you should use UNC instead of explicit mappings in the DSN. That would prevent this kind of confusion.