>>2. You are specifying a DSN entry as well as connection string parameters. Do your users have this DSN entry in their ODBC configuration? I am guessing that VFP is using the DSN entry to get the driver information. Can you specify Driver={Microsoft dBase Driver (*.dbf)} or Driver={Microsoft dBase VFP Driver (*.dbf)} in your connection string instead?
>
>I think that you've hit the puppy on the head with this one. I haven't figured a way in VFP to specify the Driver in my connection string. Do you know what the syntax would look like?

The syntax I specifed above should work for the driver parameter.

lcstring = [Driver={Microsoft dBase Driver (*.dbf)};]+;
   [DBQ=C:\GoldMine\GMbase;DefaultDir=C:\GoldMine\GMbase;DriverId=533;]+; 
   [MaxBufferSize=2048;PageTimeout=600;]
nSQL = sqlstringconnect(lcstring)

>
>But you are correct in your assumption. I assumed that everyone that had Windows had those User DSN's. I know that I didn't install them and I made the assumption that they were installed with the operating system. I want to think now that they were installed when I installed Microsoft Office 2000. I believe that it installs them so that you can do merge documents with different data sources. Can you confirm or deny as to where, specifically, the dBase Files User DSN came from?

I'm not sure when they get installed. Perhaps when specifying importing/exporting in the Visual Studio installation. I don't know if they would get installed with Office unless it is an option of Excel.