-
1
- #1
psemianonymous
Programmer
I've written a FAQ on how to set up Word mailmerge documents so you can use them like Access reports - where you call a function, and it runs the merge and displays the 'report' to you, on demand. So you can, in essence, move particularly tricky reports to Mailmerge format, and use this functionality to call them, with as few hassles as possible. For those of us who must generate 'form'-looking reports, or for those of us who must change the content and formatting of the report on a weekly basis (yes, in my case literally), or for the users who demand tweakable, e-mailable reports, with no hassles, this is useful.
This uses late binding, so is (simultaneously) compatible with all Office versions 97 and newer. Some of your users can be using 97, some of your users 2000, others 2002 or 2003, and it makes no difference to this code. Tested/used here with 97 and 2000.
Multiuser-friendly, as much as is possible. I've thought of some ways to make this more multiuser friendly (e.g. copy the mailmerge document to a local temp directory, then run the mailmerge from there), but dismissed them as useless. I haven't managed to test what happens if two or more users happen to run the same mailmerge at the same time, but let me know if you find a (quick and easy) solution.
As of now, the only hassle of any sort is that the mailmerge documents themselves--to edit them, you must re-set their data sources every time. Besides that, it's been smooth sailing, something you don't often hear with this sort of functionality.
'Native' mailmerge reports - as painless as possible
faq181-5088
Pete
This uses late binding, so is (simultaneously) compatible with all Office versions 97 and newer. Some of your users can be using 97, some of your users 2000, others 2002 or 2003, and it makes no difference to this code. Tested/used here with 97 and 2000.
Multiuser-friendly, as much as is possible. I've thought of some ways to make this more multiuser friendly (e.g. copy the mailmerge document to a local temp directory, then run the mailmerge from there), but dismissed them as useless. I haven't managed to test what happens if two or more users happen to run the same mailmerge at the same time, but let me know if you find a (quick and easy) solution.
As of now, the only hassle of any sort is that the mailmerge documents themselves--to edit them, you must re-set their data sources every time. Besides that, it's been smooth sailing, something you don't often hear with this sort of functionality.
'Native' mailmerge reports - as painless as possible
faq181-5088
Pete
