I only tried to code automation to push .csv files into an existing MailMerge Word document, then print the resultant merged document sheets to a default printer, all fired through VFP. That was for Office97, back in 2000 (I did not have Office 2000 yet, and most of my clients were using Office 97). I got it to work quite nicely, other than the Win98 Print Spooler hanging once in a while. Then Office 2000 came out, and I tried to run my automation. Gawd, it was an ugly sight. Nothing worked properly, and trying to fix it was so overwhelming.... I decided then and there that I was done trying to code for Office automation. I was not about to recode all the stuff needed to bring Office97 functionality to Office 2000.
Even after getting the one book re: VFP Automation to see how others were handling that challenge, I ended up deciding it not worth the grief. My clients would just need to learn how to do MailMerge from within Word, that was that. Luckily I had not promised my clients a Push-To-MailMerge ability. A colleague (not Ed) had suggested it to me. The good news is I do not feel compelled to provide that capability to anyone. The bad news is I burned an incredible amount of time on the automation project, and learned it was best to not try doing it again. Of course, if a client were to want that capability, and had a few gazillion dollars to waste for each hour I burned off (and billed for, and collected for), I may be willing to do it. But only if the client ignored my warnings about engaging such a project. Actually, I would suggest the client go elsewhere, it is not worth compromising myself at any price. Uggghhh. What awful memories! I relearned an old saying of mine, "Just because it can be automated does not mean it makes sense to do so." Gil > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of MB Software Solutions > Sent: Friday, June 22, 2007 4:43 PM > To: [EMAIL PROTECTED] > Subject: Re: Automation with Word 2007 > > > Ted Roche wrote: > > OLE Automation of MS Office has broken existing with nearly every > > release of MS Office. > > > And that's why I stopped going the automation route---they (M$) caused > me tons of headaches and BS support hours (UNPAID!) wasted on it. > > > -- > Michael J. Babcock, MCP > MB Software Solutions, LLC > http://mbsoftwaresolutions.com > http://fabmate.com > "Work smarter, not harder, with MBSS custom software solutions!" > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
