Until a recent security update, I was able to merge data from an Access 97
database into a Word 2002 document. After the update, I get a "5852" error -
requested object is not available." Right after the update, I was unable to
even merge the data on the server itself, i.e., bypassing Terminal Services.
By disabling the SQL script warnings, I got that part working. However, the
automation still will not work thru terminal services. I believe the security
patch was about jpeg issues, but the microsoft link also updated Office XP to
the latest SP patch. Has anyone else encountered this or have an idea how to
resolve? Currently I have my users opening Word first and manually merging
the data. Ideally, the database opens Word, opens the selected document, and
then begins the auto-open macros.

Cheryl,
I'm sure the Service Pack for Office is the culprit. Maybe this link
will help you.

http://support.microsoft.com/default...b;en-us;828499

Mike D
"Cheryl" <(E-Mail Removed)> wrote in message
news:525C112B-3E02-43CC-9714-(E-Mail Removed)...
> Until a recent security update, I was able to merge data from an Access 97
> database into a Word 2002 document. After the update, I get a "5852"
> error -
> requested object is not available." Right after the update, I was unable
> to
> even merge the data on the server itself, i.e., bypassing Terminal
> Services.
> By disabling the SQL script warnings, I got that part working. However,
> the
> automation still will not work thru terminal services. I believe the
> security
> patch was about jpeg issues, but the microsoft link also updated Office XP
> to
> the latest SP patch. Has anyone else encountered this or have an idea how
> to
> resolve? Currently I have my users opening Word first and manually merging
> the data. Ideally, the database opens Word, opens the selected document,
> and
> then begins the a uto-openmacros.

I saw that one, but it's not quite what's happening to me. The macros work if
I merge them directly on the server (once I disabled the warning messages in
the registry, that is). I only get the error messages if I'm trying to run
them thru Terminal Services. And it used to work just fine! I think you're
right though; Service Pack for Office is the cause of these troubles. I'm
just out of ideas on how to fix it.

"Mike D" wrote:

> Cheryl,
> I'm sure the Service Pack for Office is the culprit. Maybe this link
> will help you.
>
> http://support.microsoft.com/default...b;en-us;828499
>
> Mike D
> "Cheryl" <(E-Mail Removed)> wrote in message
> news:525C112B-3E02-43CC-9714-(E-Mail Removed)...
> > Until a recent security update, I was able to merge data from an Access 97
> > database into a Word 2002 document. After the update, I get a "5852"
> > error -
> > requested object is not available." Right after the update, I was unable
> > to
> > even merge the data on the server itself, i.e., bypassing Terminal
> > Services.
> > By disabling the SQL script warnings, I got that part working. However,
> > the
> > automation still will not work thru terminal services. I believe the
> > security
> > patch was about jpeg issues, but the microsoft link also updated Office XP
> > to
> > the latest SP patch. Has anyone else encountered this or have an idea how
> > to
> > resolve? Currently I have my users opening Word first and manually merging
> > the data. Ideally, the database opens Word, opens the selected document,
> > and
> > then begins the a uto-openmacros.
>
>
>