Hi Zahid,

Thanks for the reply. After reading all the threads, it seems to me that Microsoft has missed the boat with File DSN. File DSN makes it easy to establish and change ODBC connections throught your enterprise, but VFP (and most other MS products) can not directly access it.

All the examples sent will work, via programming string parsing and/or API calls. Ugly at best.

Thanks you all for the help.

Will you be able to make the User Group meeting tonight? Maybe we can see how the VB guys to it :)

Mark W. Holmes

>Mark -
>
>Not having used a file DSN, I don't know the "right" way to do this ... however, if you can't determine the "right" way, you can read the file using your favorite text-parsing tool (such as ALINES) and then use the API call SQLConfigDataSource (documented in the UT API section) to create a User DSN which is a clone of the File DSN.
>
>The main drawback of this approach (besides that it's a kludge!) is that I can't tell you how to delete the User DSN you created. However, I imagine there is an API call for that too.
>
>If you find a better way, let me know; if not, let me know how this worked for you!
>zahid
>
>>How do you connect to a file data source using SPT?
>>
>>SQLConnect('xyz') works fine with User and/or System DSN but not File DSN.