Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Word / Mailmerge and Fax / December 2007

Tip: Looking for answers? Try searching our database.

Mail merge Office 2000 to 2003

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Richard John - 02 Dec 2007 14:47 GMT
Can someone please help me out here. A meilmerge application I built
using Office 2000 (Access, Excel, Word), all worked perfectly ... until
the site upgraded to Office 2003, which now refuses to recognise the
data source programmatically which now has to be specified each time.
I've checked KB 885832 which clearly says SP2 has fixed the problem.
I've got SP3, but still no solution. The problem persists whether the
application resides on a LAN or on a local PC.

The merge documents work when operated manually, however. So now my
workaround has been to advise users to generate the data source from
Access as per usual and then jump to the desktop and use short cuts to
run the merge(s)... all very frustrating given that these upgrades are
meant to facilitate and improve productivity, not impede it, like Office
2003 has done (the problems with Office 2003 just go on and on. It
really is a croc). But I am obliged to provide a solution. All of this
previously happened automatically in Office 2000.

Any advice appreciated

TIA

Richard John
Melbourne, Australia
Peter Jamieson - 02 Dec 2007 16:38 GMT
It's more likely that the problem is actually related to this article

http://support.microsoft.com/kb/825765/en-us

Signature

Peter Jamieson
http://tips.pjmsn.me.uk

> Can someone please help me out here. A meilmerge application I built using
> Office 2000 (Access, Excel, Word), all worked perfectly ... until the site
[quoted text clipped - 19 lines]
> Richard John
> Melbourne, Australia
Richard John - 03 Dec 2007 11:17 GMT
> It's more likely that the problem is actually related to this article
>
> http://support.microsoft.com/kb/825765/en-us

Thanks Peter. The information was most useful. The dialog box mentioned
in the article is exactly what we were getting. It got me off the hook a
bit. I have to now convince Tech support to allow me to apply the
suggested solution because of the "security" implications ... :-)

Regs

Richard John
rjbpond@bigpond.net.au
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.