Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 577
  • Last Modified:

vfp-9 ole word automation error with word 2010/acrobat x

Hi:
I have a VFP app that uses OLE word automation to merge data and create/print documents. It has worked for years with WIN-XP and Office-2003 with Acrobat Standard-6.

We are now upgrading to Win-7 and Office-2010 with Acrobat Standard-X (10). Even after many internet searches and changes to Word settings, etc., my program will not run and returns error #1429. It keeps saying 'unable to run the specified macro', which is Adobe PDFMaker. yet the macro is listed in the Word Add-Ins and everything looks OK. I have also checked "enable ALL" macros in Word AND downgraded Office-2010 to the 32bit version.

Here is the code:

  oWord = CreateObject("Word.Application")
 
     WITH oWord
      .Run("AdobePDFMaker.AutoExec.Main")
      .Documents.Open((M_Doc))                                    && Open Copy of Master
      .Documents((M_Doc)).Activate
      .Documents((M_Doc)).MailMerge.Execute                && Run the merge
      .Documents((M_Doc)).Close                                    && Close Copy of Master
      .ActiveDocument.SaveAs(sys(5)+ALLTRIM(M_NewLoc)+ALLTRIM(M_NewName))      && Save new Document
 
      .Visible = .T.                  && View for editing/printing/re-saving/closing
      .Activate()
          
      ENDWITH
        
  RELEASE oWord

Any help would be greatly appreciated - really in a bind here.

Thanks.

Cathie
NYC
0
ramramcat
Asked:
ramramcat
  • 4
  • 3
1 Solution
 
pcelbaCommented:
I suppose the error is reported on the  ".Run( ... )" line.

How the Word macro uses Adobe Acrobat? I suppose via OLE automation. Then you have to use Adobe Acrobat Professional because the Standard version does not support OLE automation.
0
 
ramramcatprogrammerAuthor Commented:
Hi,
I downloaded and installed Acrobat-XI Professional (was not able to get a trial download of Acrobat-X Pro), but still am unable to run the above code; .

Is there a way to create mail-merge letters programmatically without referencing PDFMaker? This was written a very long time ago and I don't remember.

Thanks.
0
 
ramramcatprogrammerAuthor Commented:
FYI, it did not work to asterisk-out the  ".Run( ... )" line.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
pcelbaCommented:
What line of code reports the error 1429?

You should also check if appropriate Word add-on is installed. Look e.g. here: http://helpx.adobe.com/acrobat/using/creating-pdfs-pdfmaker-windows.html

If everything fails then remember you don't need Acrobat to create PDF output. You may use almost any PDF printer driver, e.g. http://www.pdfforge.org/pdfcreator

And finally you should be able to save the Word document as PDF directly:
http://www.robvanderwoude.com/vbstech_automation_word.php
http://msdn.microsoft.com/en-us/library/office/ff839952%28v=office.15%29.aspx

Mailmerge from FoxPro was described many times:
http://www.tek-tips.com/viewthread.cfm?qid=1500523
http://www.tomorrowssolutionsllc.com/Conference%20Sessions/Automating%20Microsoft%20Word.pdf

Tamar's code samples and other papers are available here: http://www.tomorrowssolutionsllc.com/publications/conferencepapers
0
 
ramramcatprogrammerAuthor Commented:
Sorry to abandon this question. Our client does not want to invest in changing their (old) VFP program to work with Win7 and is keeping the program on a Win-XP PC for now.

I'm not sure what to do with the question and points.

Thanks.
0
 
pcelbaCommented:
Yes, new operating system and other necessary software brings certain incompatibilities and you have to update the FoxPro app code and/or use different add-on software. That's the reality for software unsupported by its vendor (VFP in Microsoft).

Community is able to find working solution but it does not mean "no work"... To stay with XP is the easiest and cheapest way. You may even use your app in Virtual PC environment with XP OS and old Office installed. Everything else can run in the new OS. You just have to evaluate possible risks. XP is also unsupported software (except some ATM versions).

Points are not important. To stay on XP is one of possible solutions. :-)
0
 
ramramcatprogrammerAuthor Commented:
We'll most likely revisit this issue in the future. Thanks for your help.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now