>I was working on this some more and using the New Data Source button, I was able to set up a data source and get it working in Word (not driving it from VFP, yet). However, I'm left with some issues:

Is that just ODBC? ODBC works, but I think I may have had problems with memos with that. And, of course, you have to worry about setting it up on the individual machines.

If you're doing this through automation, why keep it as a VFP table? Why not first export to something more universal, like DBase or Excel?



>
>1) How will this work for the workstations on the network? Would I have to set up a data connection on each individual computer? It seems that MS, in trying to make this "better", has made it more difficult.
>
>2) What I'd really like to do is not connect the document to a data source. I believe I can save it as a regular document and then connect to a data source via Automation at runtime to allow for more flexibility.
>
>Still investigating . . . I think I'm making this too hard.
>
>Thanks for your reply,
>
>Russell
>
>
>>Russell,
>>
>>> but unfortunately I'm not seeing a solution (not so far, at least).
>>
>>
>>Okay, It's been awhile since I did this, but this is how I got it to work...
>>
>>There should be a "Microsoft Visual Foxpro Table"(or something like that) option when you choose the data to merge. If not, run setup again and make sure to choose all of the import filters. Now, you'll notice that all of the other import options have "...(*.DBF)" but the Foxpro one doesn't have the "(*.dbf)" after the name.
>>
>>Regedit and search the registry for the string "Microsoft Visual Foxpro Table" (or whatever the exact string is in the import options.) and change it to "Microsoft Visual Foxpro Table (*.dbf)" (Or whatever + the extension info)
>>
>>Hard to believe it's this stupid, huh?