OK, be prepared because this one is truly weird..

My server is running SQL 2000 SP2 and I have a linked server set up pointing to some VFP data through either ODBC or OLEDB. Here are the cases and results:

1. Using OLEDB, our server runs into a problem with USER32.DLL and craps out. It's impossible to get data using the OLEDB driver. Would SQL2K SP3 address this??

2. Using ODBC, if the path to the DBC uses a drive letter mapping then data retrieval works fine from the server console itself and from a remote workstation using Query Analyzer.

3. Using ODBC, if the path to the DBC uses UNC then the data retrieval works fine from the server console, but accessing from a remote workstation produces an ODBC error stating that the provider cannot open the DBC file. What in the world is up with that??

If anyone could shed any light on this I would highly appreciate it, as this is beginning to raise some serious eyebrows at a new client site and makes VFP look "that much better".

Laterness,
Jon