>I wish I could, but I never had this problem. YOu might try the MSKB for Word, this is how I resolved my problem...
>
>
>>Erik, I found this old message and was hoping you might be able to help me. I have a mail merge that use to work. Now when I open the form1.doc Word is telling me that is can not find the source, which is a table1.dbf. table1.dbf is there. Then I tried a test to create a new mailmerge. The drop down list for the data source did not have any vfp *.dbf entries. I have vfp drivers in my odbc icon on control panel, but it seems that Word does not recognize them. Any ideas?
>>
>>Brenda
>>
>>
>>>HI,
>>>I created a document that use Mail Merge with WORD 97 and VFP5 SP3. However, when I try to use VFP6 SP3, Word is telling me that the ISAM Driver is not found. What is the problem ?
>>>
>>>Thank you for your help,
>>>Christian Cote
>>
>>MDAC 2.1 dropped ODBC support for FP 2x tables. Make sure your merge files are VFP 5/6 format, and try selecting a different driver in the Word Merge dialog.
To solve the problem of the ISAM, we did the following. (in a rush... maybe improvement is needed)
*-- Verify if already done
*-- Export registry (doesn't seem to work if the folder doesn't exist or more than 8 characters.)
*-- Modify Software\ODBC\ODBC.INI\ODBC Data Sources", HKEY_CURRENT_USER
*-- Delete the old "Software\ODBC\ODBC.INI\FoxPro Files", HKEY_CURRENT_USER
*-- Recreate and adjust the "Software\ODBC\ODBC.INI\FoxPro Files", HKEY_CURRENT_USER
*-- Copy VFPODBC.DLL in c:\windows\system. This part is not included here because it is done in another class, where it validates that the copied file is not older.
*-- Because we modified "Software\ODBC\ODBC.INI\FoxPro Files" we didn't touch our Word documents.
SET classlib to registry ADDI && found in VFP ffc
LOCAL loRegistry
LOCAL lsSaveReg, lsValue
LOCAL lnResult
LOCAL ARRAY laOldreg[1]
loRegistry = CREATEOBJECT("FoxReg")
WITH loRegistry
lnResult = .GetRegKey("Analystik", @lsValue, ;
"Software\ODBC\ODBC.INI\FoxPro Files", HKEY_CURRENT_USER)
IF !(lnResult == 0) && La modif n'a pas été faite par Analystik
*-- lsSaveReg = THIS.PathNewData + "OldFoxReg.Reg"
lsSaveReg =
+ "OldFoxReg.Reg"
*-- Export les registry dans le nouveau folder SUM
RUN regedit /e &lsSaveReg. "HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\FoxPro Files"
*-- We need to do DeleteKeyValue (even if it fails) before we do the DeleteKey (we think it is some sort of initialization)
.DeleteKeyValue("test", "Software\ODBC\ODBC.INI\test\test5", HKEY_CURRENT_USER )
.DeleteKey(HKEY_CURRENT_USER, "Software\ODBC\ODBC.INI\FoxPro Files" )
.SetRegKey("FoxPro Files", "Microsoft Visual FoxPro Driver (*.dbf)", ;
"Software\ODBC\ODBC.INI\ODBC Data Sources", HKEY_CURRENT_USER)
*-- Crée la clé qu'on vient d'effacer
.OpenKey("Software\ODBC\ODBC.INI\FoxPro Files", HKEY_CURRENT_USER, .T.)
.SetRegKey("Driver", "C:\WINDOWS\SYSTEM\VFPODBC.DLL", ;
"Software\ODBC\ODBC.INI\FoxPro Files", HKEY_CURRENT_USER)
.SetRegKey("SourceDB", "c:\SUM\temp", ;
"Software\ODBC\ODBC.INI\FoxPro Files", HKEY_CURRENT_USER)
.SetRegKey("Description", "", ;
"Software\ODBC\ODBC.INI\FoxPro Files", HKEY_CURRENT_USER)
.SetRegKey("SourceType", "DBF", ;
"Software\ODBC\ODBC.INI\FoxPro Files", HKEY_CURRENT_USER)
.SetRegKey("BackgroundFetch", "Yes", ;
"Software\ODBC\ODBC.INI\FoxPro Files", HKEY_CURRENT_USER)
.SetRegKey("Exclusive", "No", ;
"Software\ODBC\ODBC.INI\FoxPro Files", HKEY_CURRENT_USER)
.SetRegKey("Null", "Yes", ;
"Software\ODBC\ODBC.INI\FoxPro Files", HKEY_CURRENT_USER)
.SetRegKey("Deleted", "Yes", ;
"Software\ODBC\ODBC.INI\FoxPro Files", HKEY_CURRENT_USER)
.SetRegKey("Collate", "Machine", ;
"Software\ODBC\ODBC.INI\FoxPro Files", HKEY_CURRENT_USER)
.SetRegKey("SetNoCountOn", "No", ;
"Software\ODBC\ODBC.INI\FoxPro Files", HKEY_CURRENT_USER)
.SetRegKey("Analystik", "Modified by Analystik due to the ISAM problem", ;
"Software\ODBC\ODBC.INI\FoxPro Files", HKEY_CURRENT_USER)
ENDIF
ENDWITH
