Welcome to SPN

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

Sign Up Now!

Linked photo files- Is it really this bad?

Discussion in 'Information Technology' started by salmonella, Nov 6, 2005.

  1. salmonella

    salmonella
    Expand Collapse
    Guest

    It seems that if I have an OLE field and I LINK a photo to it, if it is a
    bitmap image, or otherwise is displayed in the forms's field, the database
    goes up in size relative to the size of the photo.

    If, however, I LINK the field/photo using an icon for the image, the size of
    the Db goes up very little, a double click of the field/icon will open the
    image..... BUT, I only get an icon for the field on a Report.

    Is there a way to show a photo in a report, (or even the form’s field), and
    NOT have the database size balloon out of control?


    Thanks!
     
  2. Loading...

    Similar Threads Forum Date
    Opinion Letter: When terrorism is falsely linked by race or religion, we all become the victims Breaking News Apr 27, 2013
    SciTech Law of Entropy Linked to Evolution of Intelligence Breaking News Apr 23, 2013
    Canada GM corn linked to early death in new study Breaking News Sep 22, 2012
    India set to ban 100 Al Qaeda-linked groups Hard Talk May 17, 2010
    Sikh News Temple linked to terrorists still active (Moldova.org) Breaking News Feb 5, 2008

  3. Douglas J. Steele

    Douglas J. Steele
    Expand Collapse
    Guest

    The sample imaging databases at http://accdevel.tripod.com illustrate three
    approaches to handling images in Access, and the download includes an
    article discussing considerations in choosing an approach. Two of the
    approaches do not use OLE Objects and, thus, avoid the database bloat, and
    some other problems, associated with images in OLE Objects.

    If you are printing the images in reports, to avoid memory leakage, you
    should also see MVP Stephen Lebans' http://www.lebans.com/printfailures.htm.
    PrintFailure.zip is an Access97 MDB containing a report that fails during
    the Access formatting process prior to being spooled to the Printer Driver.
    This MDB also contains code showing how to convert the contents of the Image
    control to a Bitmap file prior to printing. This helps alleviate the "Out of
    Memory" error that can popup when printing image intensive reports.

    If you've already starting storing images in your database, and you'd like
    to export them all, see: http://www.lebans.com/oletodisk.htm

    --
    Doug Steele, Microsoft Access MVP
    http://I.Am/DougSteele
    (no e-mails, please!)



    "salmonella" <uwimdl@hotmail.com.dns> wrote in message
    news:EDF21D90-6D3D-4477-861D-8536AFD6D592@microsoft.com...
    >
    > It seems that if I have an OLE field and I LINK a photo to it, if it is a
    > bitmap image, or otherwise is displayed in the forms's field, the database
    > goes up in size relative to the size of the photo.
    >
    > If, however, I LINK the field/photo using an icon for the image, the size
    > of
    > the Db goes up very little, a double click of the field/icon will open the
    > image..... BUT, I only get an icon for the field on a Report.
    >
    > Is there a way to show a photo in a report, (or even the form's field),
    > and
    > NOT have the database size balloon out of control?
    >
    >
    > Thanks!
    >
     
  4. salmonella

    salmonella
    Expand Collapse
    Guest

    Thanks again Doug!

    Took a quick look at it and it seems like it will get me started.

    Many Thanks!



    "Douglas J. Steele" wrote:

    > The sample imaging databases at http://accdevel.tripod.com illustrate three
    > approaches to handling images in Access, and the download includes an
    > article discussing considerations in choosing an approach. Two of the
    > approaches do not use OLE Objects and, thus, avoid the database bloat, and
    > some other problems, associated with images in OLE Objects.
    >
    > If you are printing the images in reports, to avoid memory leakage, you
    > should also see MVP Stephen Lebans' http://www.lebans.com/printfailures.htm.
    > PrintFailure.zip is an Access97 MDB containing a report that fails during
    > the Access formatting process prior to being spooled to the Printer Driver.
    > This MDB also contains code showing how to convert the contents of the Image
    > control to a Bitmap file prior to printing. This helps alleviate the "Out of
    > Memory" error that can popup when printing image intensive reports.
    >
    > If you've already starting storing images in your database, and you'd like
    > to export them all, see: http://www.lebans.com/oletodisk.htm
    >
    > --
    > Doug Steele, Microsoft Access MVP
    > http://I.Am/DougSteele
    > (no e-mails, please!)
    >
    >
    >
    > "salmonella" <uwimdl@hotmail.com.dns> wrote in message
    > news:EDF21D90-6D3D-4477-861D-8536AFD6D592@microsoft.com...
    > >
    > > It seems that if I have an OLE field and I LINK a photo to it, if it is a
    > > bitmap image, or otherwise is displayed in the forms's field, the database
    > > goes up in size relative to the size of the photo.
    > >
    > > If, however, I LINK the field/photo using an icon for the image, the size
    > > of
    > > the Db goes up very little, a double click of the field/icon will open the
    > > image..... BUT, I only get an icon for the field on a Report.
    > >
    > > Is there a way to show a photo in a report, (or even the form's field),
    > > and
    > > NOT have the database size balloon out of control?
    > >
    > >
    > > Thanks!
    > >

    >
    >
    >
     

Share This Page