Re: mailmerge in Word 2002 fails
From: Peter Jamieson (pjj_at_KillmapSpjjnet.demon.co.uk)
Date: 02/23/05
- Next message: SonicDBA via OfficeKB.com: "Skipping records"
- Previous message: Peter Jamieson: "Re: Merging past the specified set values"
- In reply to: chris_at_oaksong.com: "Re: mailmerge in Word 2002 fails"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 23 Feb 2005 08:54:20 -0000
Sorry for the delayed response.
The only suggestion I can make is that I think with the OpenDataSource code
you are using, Word will try to open the database using DDE - in other
words, it will start Access, get it to open the database, then get the data
via DDE. Is your application definitely doing that on the user workstations
(for example, if Access pops up any dialog boxes during this process - e.g.
a password dialog, or a parameter dialog box if you are connecting to or
issuing a parameter query -they may pop up behind Word and the user may not
see them. That sounds unlikely, since you would probably experience the
problem too, and your users would probably see a more visible sign of
failure eventually, but it is worth checking).
In fact, if your Access database is secured in any way (by a password, or
using workgroup security) connection will be more difficult.
> In a sense the
> whole business seems a little whacked. Why would MS provide the
> facilities and then suddenly decide this is a security issue and
> essentially disable the capability without notifying developers?
Well, I can't answer for MS as I don't work for them, but in essence "the
facilities" (i.e. to connect to external databases) have been there from an
early version of Word but they have always relied on a bit of SQL being
issued or a converter being run, and since they are not necessarily part of
Word (and may not even be MS software) there is no guarantee that they will
work as you expect. MS has tried to fix the problem by providing a warning
mechanism within Word and allowing system administrators to disable it -
i.e., in principle the warning mechanism should only be disabled if the
administrator is convinced that insecure code will not run as the
consequence of (say) an Access SQL query running some user-defined Access
VBA macro code. Tall order, IMO.
However, from what you say it does not sound as if this particular issue is
the cause of the problem.
Peter Jamieson
<chris@oaksong.com> wrote in message
news:1108759600.616804.5150@f14g2000cwb.googlegroups.com...
> Sorry. I forgot to mention that I did a regedit on my machine to look
> for the indicated entry. I have Office XP with the indicated SP3, but
> there's no SQLSecurityCheck option in the registry. In a sense the
> whole business seems a little whacked. Why would MS provide the
> facilities and then suddenly decide this is a security issue and
> essentially disable the capability without notifying developers? (That
> may be a rhetorical question expressing my continuing frustation with
> MS.)
>
- Next message: SonicDBA via OfficeKB.com: "Skipping records"
- Previous message: Peter Jamieson: "Re: Merging past the specified set values"
- In reply to: chris_at_oaksong.com: "Re: mailmerge in Word 2002 fails"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
