>The following submitted to MS Online Support. Anybody here have any ideas on this?
>
>I am running a Visual Foxpro app that calls Word as an automation server to print invoices, proposals, purchase orders and the like. A VBA program in Word uses the Insert Database command. All VFP memo fields are truncated to 255 character length; this did not happen in Word 97. I referenced KB Q242072 and it gives a "Workaround" which only works with Access data--totally useless. I was told yesterday that the first service release for Office 2000 would correct this issue, but when I asked "when?", was only told first quarter. That could be three months away. I was told to reload Word 97 and call it using GetObject() instead of my current CreateObject().That does not work. The Help file for GetObject specifically says "The application does not need to be specified, because the OLE dynamic link libraries determine the application to start based on the file name you provide." When I try to use the first parameter to specify the file location for the Word 97 winword.exe, I get an OLE
>error code 0x80004002, "No such interface supported." Leaving off the first (filename) parameter in GetObject simply starts an instance of Word 2000. I assume there's a registry entry that determines OLE automation server paths, but a search of the registry for my system's winword.exe pathname turns up what appears to be dozens of locations--too many for me to experiment blindly with. So how can I temporarily force the useof Word 97 until this mess gets fixed in Word 2000? (Please tell me it IS going to be fixed--the current situation is a gigantic disaster!)

---

Ray,
As an addition to John I do not use "insert database" for ODBC problems. Instead I write the data that would be transfered either to a file or clipboard tab delimited, replacing "carriage returns" in memo with a tilde. Then I paste in word, convert texttotable, replace tilde with CR back.
Cetin