Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

View .jpg in Forms

Discussion in 'Information Technology' started by Warren King, Jul 28, 2006.

Tags:
  1. Warren King

    Warren King
    Expand Collapse
    Guest

    We have a database that was created in Access 2000 with a form that displays
    employee information including a picture. Everything worked fine until we
    updated client computers to Access 2003. Now the form will display pictures
    that already existed in the database but will not allow us to edit the
    picture by double clicking it. We get an error that says the OLE object is
    not registered. The table view that holds the picture field shows all the
    jpeg pictures to be MSPhotoEd.3 and that object does not show in the list
    that comes up to register from. When adding a new employee with Access
    2003, the picture field now shows it is a "package", but does not display in
    the form!

    So I have 2 problems, 1) we can not edit existing photos and 2) we can not
    display new photos.

    Any suggestions as to what I can do to fix these problems?

    Warren
     
  2. Loading...

    Similar Threads Forum Date
    Ashdoc's Movie Review---Force 2 Theatre, Movies & Cinema Nov 20, 2016
    Ashdoc's Movie Review---Rock On 2 Theatre, Movies & Cinema Nov 13, 2016
    Movies Alternate View - Review Of 'PROMETHEUS' Theatre, Movies & Cinema Nov 12, 2016
    Ashdoc's Movie Review---Mr Church Theatre, Movies & Cinema Nov 5, 2016
    Ashdoc's Movie Review---Ae Dil Hain Mushkil Theatre, Movies & Cinema Nov 1, 2016

  3. bob

    bob
    Expand Collapse
    Guest

    Access 2003 does not include the typical OLE Server application for JPEG (MS Photo Editor), and if you
    install Office 2003 as an upgrade it will remove Photo Editor if present. You can re-install Photo Editor
    from your Office XP disks to get the app working again.

    You should note that there are several other potentially serious problems with this approach to storing
    images, most notably that the images are stored uncompressed and therefore occupy anything up to 50 or
    100 *times* the original file size (with a corresponding performance overhead).

    --
    _______________________________________________________
    DBPix 2.0: Add pictures to Access, Easily & Efficiently
    http://www.ammara.com/dbpix/access.html




    "Warren King" <warrenk@egglestonservices.org> wrote:
    >We have a database that was created in Access 2000 with a form that displays
    >employee information including a picture. Everything worked fine until we
    >updated client computers to Access 2003. Now the form will display pictures
    >that already existed in the database but will not allow us to edit the
    >picture by double clicking it. We get an error that says the OLE object is
    >not registered. The table view that holds the picture field shows all the
    >jpeg pictures to be MSPhotoEd.3 and that object does not show in the list
    >that comes up to register from. When adding a new employee with Access
    >2003, the picture field now shows it is a "package", but does not display in
    >the form!
    >
    >So I have 2 problems, 1) we can not edit existing photos and 2) we can not
    >display new photos.
    >
    >Any suggestions as to what I can do to fix these problems?
    >
    >Warren
    >
    >
     
  4. Warren King

    Warren King
    Expand Collapse
    Guest

    Thanks for the reply. I guess my next question is how do you get a photo to
    display in an Access form and Access report? All we can see is the image
    name.



    "bob" <exponent@hotmail.com> wrote in message
    news:44990d97$1@news.ammara.com...
    >
    >
    > Access 2003 does not include the typical OLE Server application for JPEG
    > (MS Photo Editor), and if you
    > install Office 2003 as an upgrade it will remove Photo Editor if present.
    > You can re-install Photo Editor
    > from your Office XP disks to get the app working again.
    >
    > You should note that there are several other potentially serious problems
    > with this approach to storing
    > images, most notably that the images are stored uncompressed and therefore
    > occupy anything up to 50 or
    > 100 *times* the original file size (with a corresponding performance
    > overhead).
    >
    > --
    > _______________________________________________________
    > DBPix 2.0: Add pictures to Access, Easily & Efficiently
    > http://www.ammara.com/dbpix/access.html
    >
    >
    >
    >
    > "Warren King" <warrenk@egglestonservices.org> wrote:
    >>We have a database that was created in Access 2000 with a form that
    >>displays
    >>employee information including a picture. Everything worked fine until we
    >>updated client computers to Access 2003. Now the form will display
    >>pictures
    >>that already existed in the database but will not allow us to edit the
    >>picture by double clicking it. We get an error that says the OLE object
    >>is
    >>not registered. The table view that holds the picture field shows all the
    >>jpeg pictures to be MSPhotoEd.3 and that object does not show in the list
    >>that comes up to register from. When adding a new employee with Access
    >>2003, the picture field now shows it is a "package", but does not display
    >>in
    >>the form!
    >>
    >>So I have 2 problems, 1) we can not edit existing photos and 2) we can not
    >>display new photos.
    >>
    >>Any suggestions as to what I can do to fix these problems?
    >>
    >>Warren
    >>
    >>

    >
     
  5. bob

    bob
    Expand Collapse
    Guest

    As mentioned, you can install Photo Editor from the Office XP disks to get things working again. If you
    want to really solve the issue (to avoid the OLE bloat, this type of app dependency/config issue, and other
    problems) then there are essentially 2 choices: work with images stored externally (in the file-system)
    or work with images stored as blobs (i.e. the ‘normal’ way, without OLE).

    Imaging without OLE in Access can use the built-in Access image control. This is not without it’s own
    drawbacks, however. It relies on the relevant Office Graphics Filters being installed, and needs registry
    tweaks on each machine to avoid a crash problem and to suppress the annoying ‘Loading Image’ dialog that
    pops-up for each record. It is also limited in the maximum image size it can handle, and will often fail
    with today’s typical digital camera images. Finally, performance can be an issue, since images are decoded
    synchronously as you scroll through records, and this is exacerbated in a code-based blob solution using
    the ‘read-from-table -> write-to-file -> read-from-file’ approach.

    Larry’s’ samples (see address below) illustrate the OLE, external files and blob (code-based) approaches:
    http://members.tripod.com/accdevel/imaging.htm

    Stephen Lebans site has a range of imaging solutions:
    http://www.lebans.com/

    …or there are commercial solutions that avoid OLE and the Access Image control altogether.


    --
    _______________________________________________________
    DBPix 2.0: Add pictures to Access, Easily & Efficiently
    http://www.ammara.com/dbpix/access.html




    "Warren King" <warrenk@egglestonservices.org> wrote:
    >Thanks for the reply. I guess my next question is how do you get a photo to
    >display in an Access form and Access report? All we can see is the image
    >name.
    >
    >
    >
    >"bob" <exponent@hotmail.com> wrote in message
    >news:44990d97$1@news.ammara.com...
    >>
    >>
    >> Access 2003 does not include the typical OLE Server application for JPEG
    >> (MS Photo Editor), and if you
    >> install Office 2003 as an upgrade it will remove Photo Editor if present.
    >> You can re-install Photo Editor
    >> from your Office XP disks to get the app working again.
    >>
    >> You should note that there are several other potentially serious problems
    >> with this approach to storing
    >> images, most notably that the images are stored uncompressed and therefore
    >> occupy anything up to 50 or
    >> 100 *times* the original file size (with a corresponding performance
    >> overhead).
    >>
    >> --
    >> _______________________________________________________
    >> DBPix 2.0: Add pictures to Access, Easily & Efficiently
    >> http://www.ammara.com/dbpix/access.html
    >>
    >>
    >>
    >>
    >> "Warren King" <warrenk@egglestonservices.org> wrote:
    >>>We have a database that was created in Access 2000 with a form that
    >>>displays
    >>>employee information including a picture. Everything worked fine until we
    >>>updated client computers to Access 2003. Now the form will display
    >>>pictures
    >>>that already existed in the database but will not allow us to edit the
    >>>picture by double clicking it. We get an error that says the OLE object
    >>>is
    >>>not registered. The table view that holds the picture field shows all the
    >>>jpeg pictures to be MSPhotoEd.3 and that object does not show in the list
    >>>that comes up to register from. When adding a new employee with Access
    >>>2003, the picture field now shows it is a "package", but does not display
    >>>in
    >>>the form!
    >>>
    >>>So I have 2 problems, 1) we can not edit existing photos and 2) we can not
    >>>display new photos.
    >>>
    >>>Any suggestions as to what I can do to fix these problems?
    >>>
    >>>Warren
    >>>
    >>>

    >>

    >
    >
     
  6. Warren King

    Warren King
    Expand Collapse
    Guest

    Thanks for your advise. I took the first suggestion of installing the Photo
    Editor from the Office XP disks and that is going to do the job for us at
    this time. We are just using this particular database to create employee ID
    cards so once we can keep the database relatively small by deleting records
    as employees leave the company. We hope to be getting an ID making machine
    in the near future that will eliminate the problem all together for us.

    "bob" <exponent@hotmail.com> wrote in message
    news:449bba38$1@news.ammara.com...
    >
    >
    > As mentioned, you can install Photo Editor from the Office XP disks to get
    > things working again. If you
    > want to really solve the issue (to avoid the OLE bloat, this type of app
    > dependency/config issue, and other
    > problems) then there are essentially 2 choices: work with images stored
    > externally (in the file-system)
    > or work with images stored as blobs (i.e. the 'normal' way, without OLE).
    >
    > Imaging without OLE in Access can use the built-in Access image control.
    > This is not without it's own
    > drawbacks, however. It relies on the relevant Office Graphics Filters
    > being installed, and needs registry
    > tweaks on each machine to avoid a crash problem and to suppress the
    > annoying 'Loading Image' dialog that
    > pops-up for each record. It is also limited in the maximum image size it
    > can handle, and will often fail
    > with today's typical digital camera images. Finally, performance can be
    > an issue, since images are decoded
    > synchronously as you scroll through records, and this is exacerbated in a
    > code-based blob solution using
    > the 'read-from-table -> write-to-file -> read-from-file' approach.
    >
    > Larry's' samples (see address below) illustrate the OLE, external files
    > and blob (code-based) approaches:
    > http://members.tripod.com/accdevel/imaging.htm
    >
    > Stephen Lebans site has a range of imaging solutions:
    > http://www.lebans.com/
    >
    > .or there are commercial solutions that avoid OLE and the Access Image
    > control altogether.
    >
    >
    > --
    > _______________________________________________________
    > DBPix 2.0: Add pictures to Access, Easily & Efficiently
    > http://www.ammara.com/dbpix/access.html
    >
    >
    >
    >
    > "Warren King" <warrenk@egglestonservices.org> wrote:
    >>Thanks for the reply. I guess my next question is how do you get a photo
    >>to
    >>display in an Access form and Access report? All we can see is the image
    >>name.
    >>
    >>
    >>
    >>"bob" <exponent@hotmail.com> wrote in message
    >>news:44990d97$1@news.ammara.com...
    >>>
    >>>
    >>> Access 2003 does not include the typical OLE Server application for JPEG
    >>> (MS Photo Editor), and if you
    >>> install Office 2003 as an upgrade it will remove Photo Editor if
    >>> present.
    >>> You can re-install Photo Editor
    >>> from your Office XP disks to get the app working again.
    >>>
    >>> You should note that there are several other potentially serious
    >>> problems
    >>> with this approach to storing
    >>> images, most notably that the images are stored uncompressed and
    >>> therefore
    >>> occupy anything up to 50 or
    >>> 100 *times* the original file size (with a corresponding performance
    >>> overhead).
    >>>
    >>> --
    >>> _______________________________________________________
    >>> DBPix 2.0: Add pictures to Access, Easily & Efficiently
    >>> http://www.ammara.com/dbpix/access.html
    >>>
    >>>
    >>>
    >>>
    >>> "Warren King" <warrenk@egglestonservices.org> wrote:
    >>>>We have a database that was created in Access 2000 with a form that
    >>>>displays
    >>>>employee information including a picture. Everything worked fine until
    >>>>we
    >>>>updated client computers to Access 2003. Now the form will display
    >>>>pictures
    >>>>that already existed in the database but will not allow us to edit the
    >>>>picture by double clicking it. We get an error that says the OLE object
    >>>>is
    >>>>not registered. The table view that holds the picture field shows all
    >>>>the
    >>>>jpeg pictures to be MSPhotoEd.3 and that object does not show in the
    >>>>list
    >>>>that comes up to register from. When adding a new employee with Access
    >>>>2003, the picture field now shows it is a "package", but does not
    >>>>display
    >>>>in
    >>>>the form!
    >>>>
    >>>>So I have 2 problems, 1) we can not edit existing photos and 2) we can
    >>>>not
    >>>>display new photos.
    >>>>
    >>>>Any suggestions as to what I can do to fix these problems?
    >>>>
    >>>>Warren
    >>>>
    >>>>
    >>>

    >>
    >>

    >
     

Share This Page