>>
>>PMFJI. WordBasic does offer one advantage if your customers use a mixture of Office 95 and Office 97. Word 95 uses only WordBasic, and Word 97 uses VBA (preferred), but Word 97 can also deal with WordBasic. So, if you use WordBasic in your code, you can reach a larger audience.
>>
>>It is also fairly easy to determine which version of Word is present. You could have two methods for your VFP-to-Word connection (one in WordBasic and the other in VBA), determine which version of Word is in use, and then execute the appropriate method.
>>
>>Of course, if you just wrote one method in WordBasic, you wouldn't care which version of Word was running, because they will both recognize WordBasic.
>>
>>Now, here's an interesting rumor I heard recently...future versions of Word will use VBA only; WordBasic will no longer be supported. I have not been able to verify this through my sources, but if it is true, then obviously one wouldn't want to use WordBasic for future development.
>>
>>Comments?
>>
>>Thanks -- Bill
>
>I've heard the same rumor. I agree about the mixed versions of Word, and if only Word 97 or later is used, VBA is the way to go.

For some bad reason VBA requires Custom installation of MS-Office, so if you develop on machine with this environment (as it's supposed to be) and then distribute to client with 'Standard' installation, the application bombs. It seems to be a great lapse.