Embedded pdf error when closing Acrobat

[sandal]

Created an OLE field in Access 2003 table. Most types of embedded
documents open and close from there fine but Acrobat 8 give an error
when closing the pdf viewer:

"The operation on the Acrobat Document object failed. The OLE
server may not be registered. To register the OLE server, reinstall
it."

I've tried several machines and all fail in the same manner. There is a
posting on this "OLE Server Issues and PDF's" dated June 19 2007 where
it's stated that registering the Adobe Acrobat 8.0 Type Library fixes
this issue but it does not for me.

Can anyone shed light on this?

 

[Nancy at BCU]

I'm having this same problem, trying to close a PDF file that is embedded in
my Access form. In addition, Access is not saving the object, but I think
that is due to the same problem of this OLE error.

 

[sandal]

I hope someone from Microsoft will respond to this. Apparently the issue
has been around for a long time. PDF is not some esoteric file format,
how can Access not support embedded PDF?

 

[Paul Shapiro]

I would guess the problem is Adobe's incomplete support for OLE, not
Microsoft's lack of support for pdf. Microsoft supports storing anything
that meets the OLE spec in an ole field.

Adobe has updates to version 8.1.2. You could check that you're on the
latest version.

Access 2003 is a bit more problematic. While it might help to be on the
latest SP, with the hotfix that corrected some of the SP problems, there is
less than universal support for SP3. You could at least make sure you're on
SP2.

 

[sandal]

I have 8.1.2. It seems that this issue is present with both Access 2000
and 2003, both on latest sp.

Does anyone find Acrobat 8.1.2 works with Access? If so I wonder what
the difference is?

(e-mail address removed) says...

 

[Albert D. Kallal]

I have to say using embedded objects like word, pdf etc. inside of a form is
a real road to an unreliable application.

the Dolby tends to issue a demonic updates quite often, and just about every
other update you get from them who tends to break something.

what happens is you get this thing working, and then a dope we will issue a
new update and Bam there goes your application again.

there is also significant other number of issues that are difficult when you
and bet the object inside of a form, the big one is you can't control
printing, you can't control what appears in a report when you try to print
(the only get the first page of the pdf printed for example).

other issues are if the user tries to navigate to fast in the form, the only
object can update the screen fast enough and falls behind (again this simply
just make sure application more buggy and reliable, and also in many cases
can significantly affect the form loads time).

Office/access comes out with a new version every three or four years, Adobe
is updated every few months, and just about every time you update the ole
inbeeded stuff breaks.

I would suggest that you store the path name to the pdf file, and place a
"view" buttion on your form.

The code can thus be:

Application.FollowHyperlink me!NameOfFieldWithPathToPdf

The above approach results in a much more robust and reliable application.
Updates to the PDF will not waste valuable support dollars and waste your
time that you could well use for other things in your life.

 

[sandal]

It's a pretty sophisticated application; there are thousands of docs and
images stored in the file system, and which are opened in the manner you
suggest. The embedded docs, if I go that route, would be used in a
separate helper application for remote users to provide "simple" access
to ref docs. The embedded docs would never be edited and would never be
shown in an Access form.

I am very familiar with the issues that embedded objects bring, but
considered for this purpose as a way to route the ref docs to remote
users. The set of embedded docs that were no longer needed would be
deleted every couple hours. It'd be a workable approach, but not if PDF
fails as badly as it does. I'd never run into an issue like this before
with embedded docs. Since I only need support for pdf and tif, it's just
bad luck that one of the two has issues.

What's the Dolby?

I'd still like to hear more from anyone that can suggest other possible
fixes for embedded pdf.

 

[Albert D. Kallal]

What's the Dolby?

I am using voice dictaon software, supposed to be adobe, and if it misses
that "ah"...you
get dolby....