VFP to doesn't launch Ms Word's mailmerge

[Jay9988]

Hi All,
I have an application to launch MS Word mailmerge.
It is using VFP class: mailmrge.vcx
with this command

WITH THISFORM._mailmerge
    .cAppTitle = "Kontrak Sewa"    && application name, used in Alerts 
    .nWordProc = 1                    && word processor (1 = Word 6+; 2 = CommaDelim; or user-defined (see below); default = 1)
    .nNewDoc = 2                    && is it a new doc (1 = new, 2 = existing; default = 1)
    .cdocname=mdrive+mfile
    .nTemplate = 1                    && type of main document (Word only, 1 = form letter; 2 = label; 3 = envelope; 4 = catalog; default = 1)
    .cAlias = ALIAS()                && alias of source table or view
    ACOPY(aflds, .aAutoFields)        && fill in array of field names to be used
    .MakeOutput()                    && do the merge
   ENDWITH

But, in several PCs the Word window doesn't launch. In other PCs works fine... The VFP ODBC driver has been installed in all the PCs

Is it anything related to Office version? Because I have 2 PC's, both using Word 2013. The one pc is work fine, and the other pc Word doesn't launch.

Does anyone know the problem ?

Many thanks

 

[TamarGranor]

Is Word actually installed on the machines where you're having a problem? Not the Click to run or Office 365 version?

Tamar

 

[Jay9988]

Is Word actually installed on the machines where you're having a problem? Not the Click to run or Office 365 version?

Tamar

Hi Tamar,
Yes, the Word is installed, and running. But in several computers, the MS WORD cannot launched from VFP using code above. VFP ODBC Driver is also installed. I have tried in 4 computers: 2 computers is using Word 2016 and 2013, and the code is running properly. The other 2 computers using Word 2013 and 2019, the mailmerge doesn't lounched.

 

[mJindrova]

Are you sure, so ODBC drivers on both PC are same? Please, compare version and file size.

 

[Mike Lewis]

How about bypassing the VFP Mailmerge class and the ODBC driver? In other words, see what happens when you do this:

loWord = CREATEOBJECT("word.applicaiton")

This will not give you the solution, but it will tell you whether it is Word (or more precisely the Word Automation server) which is at fault, or the VCX or ODBC driver.

 

[TamarGranor]

How about bypassing the VFP Mailmerge class and the ODBC driver? In other words, see what happens when you do this:

loWord = CREATEOBJECT("word.applicaiton")

This will not give you the solution, but it will tell you whether it is Word (or more precisely the Word Automation server) which is at fault, or the VCX or ODBC driver.

Just pointing out a minor typo in Mike's code that would give you trouble in a cut-and-paste. Should be:

loWord = CREATEOBJECT("word.application")

Tamar

 

[Mike Lewis]

Thanks for that, Tamar.

Mike