Default Field Size question?

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

    Default Field Size question?

    Greetings all,

    Despite the inefficiency, I am content to cut and paste 20Kb JPEG images
    into a OLEBound field in my inventory DB (because I don't want subsequent
    users to have the hassle of loading and linking to other applications -
    after my death).

    I am surprised to see that the size of the Access mdb file increases by
    about 1Mb for every 4 images added.

    I don't suppose I will include more than 2000 images and the resulting
    mdb file should fit on a single CD-R; no problem?

    However, as a beginner here, I'm curious, is there any limit to the size
    of an mdb file?

    Is there some default (field / memory) size that I could safely reset to
    a lower figure to store more images per Mb.

    Kind regards

    Tony E


  • Pieter Linden

    #2
    Re: Default Field Size question?

    "Rednelle" <rednelle31@bti nternet.com> wrote in message news:<cfinro$dm k$1@sparta.btin ternet.com>...[color=blue]
    > Greetings all,
    >
    > Despite the inefficiency, I am content to cut and paste 20Kb JPEG images
    > into a OLEBound field in my inventory DB (because I don't want subsequent
    > users to have the hassle of loading and linking to other applications -
    > after my death).
    >
    > I am surprised to see that the size of the Access mdb file increases by
    > about 1Mb for every 4 images added.
    >
    > I don't suppose I will include more than 2000 images and the resulting
    > mdb file should fit on a single CD-R; no problem?
    >
    > However, as a beginner here, I'm curious, is there any limit to the size
    > of an mdb file?
    >
    > Is there some default (field / memory) size that I could safely reset to
    > a lower figure to store more images per Mb.
    >
    > Kind regards
    >
    > Tony E[/color]

    Search the NG for this one, or ask Larry Linson. Storing the images
    inside your database is completely nuts. It will get enormous very
    fast. If all of this stuff will be one the CD, use App.Path or
    whatever to get the path to the MDB and figure out the path to the
    images from there, and just store what you have to.

    Comment

    • Rednelle

      #3
      Re: Default Field Size question?

      Thanks for the advice Pieter, I'll take it and contact Larry Linson

      Kind regards

      Tony E

      "Pieter Linden" <pietlinden@hot mail.com> wrote in message
      news:bf31e41b.0 408131809.6eec3 506@posting.goo gle.com...[color=blue]
      > "Rednelle" <rednelle31@bti nternet.com> wrote in message[/color]
      news:<cfinro$dm k$1@sparta.btin ternet.com>...


      Comment

      • Larry Linson

        #4
        Re: Default Field Size question?

        "Rednelle" wrote
        [color=blue]
        > Thanks for the advice Pieter, I'll
        > take it and contact Larry Linson[/color]

        You just did. :-)

        The example databases at http://accdevel.tripod.com (one for Access
        97, a second for Access 2000 and later) illustrate three approaches to
        handling images in Access, two of which do not cause the "bloat" that
        you have observed. The included article explains why you see that
        bloat.

        I am away from my office machine with the exact hyperlink to MVP
        Stephen Lebans' website, but you will find example code there to avoid
        running out of memory when Reporting using other than .BMP image files
        (it shows how to convert your files to BMP just before using them in
        the Report). I believe you will also find a control to display images
        if your users do not have the graphics filters installed.

        Best of luck with your project.

        Larry Linson
        Microsoft Access MVp

        Comment

        • Pieter Linden

          #5
          Re: Default Field Size question?

          larry.linson@nt pcug.org (Larry Linson) wrote in message news:<fcc4f276. 0408141419.4df2 e8bd@posting.go ogle.com>...[color=blue]
          > "Rednelle" wrote
          >[color=green]
          > > Thanks for the advice Pieter, I'll
          > > take it and contact Larry Linson[/color]
          >
          > You just did. :-)
          >
          > The example databases at http://accdevel.tripod.com (one for Access
          > 97, a second for Access 2000 and later) illustrate three approaches to
          > handling images in Access, two of which do not cause the "bloat" that
          > you have observed. The included article explains why you see that
          > bloat.
          >
          > I am away from my office machine with the exact hyperlink to MVP
          > Stephen Lebans' website, but you will find example code there to avoid
          > running out of memory when Reporting using other than .BMP image files
          > (it shows how to convert your files to BMP just before using them in
          > the Report). I believe you will also find a control to display images
          > if your users do not have the graphics filters installed.
          >
          > Best of luck with your project.
          >
          > Larry Linson
          > Microsoft Access MVp[/color]




          see, I told ya Larry would have that link... =)

          Comment

          Working...