>Rick,
>
>The problem is the ODBC drivers - a new data access pack appears to be automatically installed with Win98 2nd Edition, VFP 6 Service Pack 3 or Office 2000.
>
>The default behavior for the new Foxpro driver will not open mailmerge files which used the "old" FoxPro Files ODBC driver.
>
>The MS knowledgebase article Q217013 - does provide the *fix* for the problem in the RESOLUTION portion of the article. It is relatively simple - but it will have to be performed on *each* machine that uses the "FoxPro Files" driver.
>
>The MS install for the DataAccessPack 2.1 program should have taken care of this for us - not the case.
The 'RESOLUTION' that is proposed in the article takes care of the DSN entries that you created using old FoxPro ODBC.
However if you used a DSN-Less connection this workaround doesn't work.
Example:
We use MSWORD .DOC pre-configured to mail-merge to determined .DBF tables.
We ship this .DOC documents with our App.
During runtime, the user can open the Document that is directed to a DBF using the DSN-Less connection provided by word in the Mail-Merge feature.
Now I can't do this.
How do I create a .DOC that can be used in any client without creating DSN's on that client ?
If someone has a workaround for this I would appreciate.
TIA
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only