I did a Search and found your meantion of this site previously. I had them run the VFPODBC.msi then wdvfpdsn.exe that the site (and MS site) suggests. My clients had a MS VFP driver probably because it is an image that someone creates and pushes down to their machines. It is not just a plain XP. It comes loaded with lots of software already installed.


>Take a look at Word Merge Feature doesn't Work in Windows XP or After >Windows XP Upgrade at http://www.visualpractice.com/xp_merge.shtml. BTW, >Windows XP doesn't have VFP ODBC driver installed.


>>My clients just upgraded to XP SP2 and they are having trouble with Word Mail Merge that uses a VFP table as the data source. When they double click on the document the mail merge is not performed. When they try to Open New Data Source to select their *.dbf file, they get "Word was unable to open the data source".
>>
>>Their MS VFP Driver was at version 1.0 and I had them run VFPODBC.msi then wdvfpdsn.ex. This brought their driver to version to 6.01. But still they are getting "Word was unable to open the data source". Now if they choose "New Data Source", "ODBC.DSN", "Visual FoxPro Tables", it adds an entry to the My Data Sources, and then the merge works. But this requires that each desktop goes through the process of creating a My Data Source for each document. (the documents and data source are on the server). Too many users and too many documents.
>>
>>Of course I have VFP on my XP, so my drivers were loaded during the VFP intall. But in my Confirm Data Source window I have entries that come from my ODBC USER DSN tab. They are not the names of my drivers directly. Tey are entries like "dbase - Word via ODBC" and "FoxPro Files - Word via ODBC". Is this important and can only your User DSN that are based on VFP VF or dbase get displayed in your Confirm data base?
>>