DJ,
It could be a couple of things.

1. Whether your users have MDAC 2.5 or not, what version of the DbaseIV ODBC driver do you use and what do they use?
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?

HTH.

>In my code I use a connection string to connect to dBase IV files. That string is this:
>
>nSQL = sqlstringconnect([DSN=dBASE Files;DBQ=C:\GoldMine\GMbase;DefaultDir=C:\GoldMine\GMbase;DriverId=533;MaxBufferSize=2048;PageTimeout=600;])
>
>This works fine on my system and all systems in our test environment. For some of my end users, however, this is not the case. The connection is failing. Is there a possibility that it works for us because we have MDAC 2.5 and it doesn't work on other systems because they may have an earlier version of MDAC? I'm grasping here trying to figure out why some systems can't make the connection.
>
>TIA
>
>DJ :o)