>Hi Tamor,
>
>I'm having a similar problem.
>
>I'm using your Office Automation code from the excellent book you wrote when you were probably only 3, since today I'm going to guess you're only 29.
First, thanks. In fact, I was well beyond 29 when I wrote that book (but I did have the pleasure over the weekend of someone telling me that I couldn't possibly be old enough to be my younger son's mother).
>
>Up until my client installed Office 2013, the code worked well, running from Word 97 through Word 2007 and lastly Word 2010. I just updated as time went on increasing the Word Version to check for and modifying the Constant variables in my foxpro.h file among other little code housekeeping changes.
>
>So when they said they've upgraded to 2013, I've made similar changes, indicating that the Version is now 15, but the code either hangs or we get a message referring to ISAM.
>
>Since as you know the code is broken up into a number of different processes which I've made into different methods of my base form class from which the mail merge is invoked from various forms, I'm not sure what code would be appropriate to post here.
>
>I read elsewhere that MS with Office 2013 has deprecated the VFP OLE and so it can no longer do merges with either Word or Excel.
>
>Bottom line, I guess, is the question: Is anyone successfully doing mail merge automation with VFP 9 SP 2 and Word 2013? If so, how?
>
> I don't currently have Office 2013 installed on my computer so I can't walk through the code to find exactly what the problem is.
>
>On more possible complicating factor is the client still has Word 2007 installed.
>
>Any help will be greatly appreciated because this client is just the first of a number of my clients who will undoubtedly be told by their IT folks to migrate to 2013 without first checking if there's any issues with VFP, and they all love the merge feature I was able to provide (using your code, of course <g>)
>
I also don't have Office 2013 installed anywhere, so can't test. The first thing I'd check for is that it's actually installed on the machine, not working through the cloud in some way.
Beyond that, you need to capture the line # and error and show us what code is producing what error.
One other thought: the mailmerge technique in the book turned out to be pretty slow; the mention of ISAM makes me wonder if it's an issue with accessing DBFs. You might try the alternate technique we posted here:
http://www.hentzenwerke.com/catalog/autofoxfaq.htmTamar
