Storing OLE

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • T23459

    #1

    Storing OLE


    Re: storing jpg images in Access.
    I have a database that requires adding pictures (jpegs) on a regular basis.
    OLE field.
    Even if they are only 320x240 large, I can see - over time, that the amount
    of space these pics will take up will be great.
    Does linking the pics still copy these pics in the database?
    Any suggestions on a practical approach to keeping the database functioning
    smoothly over the coming years with the regular addition of pics on a
    regular basis ?
    thanks


  • pietlinden@hotmail.com

    #2
    Re: Storing OLE

    where's Larry Linson's canned response to this?
    Short answer - don't store your images in the database, just link to
    them. You can use the OpenSaveFile API to grab the path to the file
    see the API section of www.mvps.org

    Comment

    • Douglas J. Steele

      #3
      Re: Storing OLE

      <pietlinden@hot mail.com> wrote in message
      news:1113700149 .648990.237560@ l41g2000cwc.goo glegroups.com.. .[color=blue]
      > where's Larry Linson's canned response to this?[/color]

      You mean:

      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.zi p 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



      <g>

      --
      Doug Steele, Microsoft Access MVP

      (no e-mails, please!)




      Comment

      • pietlinden@hotmail.com

        #4
        Re: Storing OLE

        Yep, thanks Doug. That's the one.

        Comment

        Working...