OLE server problem in Office 2003

  • Thread starter Thread starter Colin
  • Start date Start date
C

Colin

Hi,

I've recently installed Office 2003 & am now unable to add picture objects
to forms in Access.

I have a number of database forms which contain picture files in jpg format.
All worked fine in Office XP.
Existing picture files still display correctly but when new pictures are
added, all I get is the filename displayed.
In the corresponding table, the data is shown as a Package instead of
Microsoft Photo Object.

I've tried doing Insert Object in Word & Excel and these also now have the
same problem.

I am fairly sure that this did work at first after the upgrade.
I thought the cause was another piece of software which I loaded later.
This installed a runtime version of Access 2000 as part of its own
installation.
However, I've since removed that software. I've also removed & reinstalled
Office 2003.
I have even reinstalled Windows XP over the existing installation in case
the problem is with the OLE server in Windows itself.
None of these attempts has solved the problem.

Can anyone please advise me what to try next.
Happy to edit File Associations or the Registry if either of these will do
the trick.

Cheers

Colin
 
You must have MS Photo Editor installed on the system AND registered for the relevant file-types/extensions.


Note that this approach usually causes a storage overhead of between 5 and 100 *times* the size of the
original jpeg files, since the image is stored uncompressed. This, and the undocumented headers, can also
make it impossible to extract the original image file, or interoperate with VB, asp, IE etc, so make sure
you keep copies of the original files !

If you want to store the images actually in the database, then storing raw image data avoids these and
other problems.
 
Hi. Thanks for your response.

I removed Photo Editor along with the rest of Office XP once I thought all
was working OK with Office 2003
There is a newer program installed with 2003 called MS Office Picture
Manager.
This seems far better than the old & clunky Photo Editor but its already
associated with all available image types & not doing what I need. I've also
got JASC Paint Shop Pro 8 installed.

Whilst I can reinstall MS Photo Editor, I'm not sure why this would help.
Can you explain please

Thanks

Colin

Exponent said:
You must have MS Photo Editor installed on the system AND registered for
Click to expand...
the relevant file-types/extensions.
Note that this approach usually causes a storage overhead of between 5 and 100 *times* the size of the
original jpeg files, since the image is stored uncompressed. This, and
Click to expand...
the undocumented headers, can also
make it impossible to extract the original image file, or interoperate
Click to expand...
with VB, asp, IE etc, so make sure
 
When you store a file using OLE Embedding, Access invokes the application that is associated with the file-type
to store the 'object'. If the application does not support OLE-Embedding, a package is created.

This type of configuration issue, along with the overhead and proprietary/extraction/interop issues, are
fairly common when using jpeg images with OLE Embedding/Linking, and hence the recommendation to use raw
binary storage instead of OLE Embedding when images are to be stored in the database.
 
Can you explain it step by step. I have the same issue. It also giving me printing problems. I sure it is becouse of the size of the out going file

----- acebaron wrote: ----

I thank you for replying. Now I have to figure out exactly what you said.
 
Back
Top