Welcome to SPN

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

Sign Up Now!
  1.   Become a Supporter    ::   Make a Contribution   
    Target (Recurring Monthly): $200 :: Achieved: $98

How to prevent access database from enlarging without limit?

Discussion in 'Information Technology' started by Bill White, Nov 8, 2005.

  1. Bill White

    Bill White
    Expand Collapse
    Guest

    I am using access database in my app to store text, picture and so on. it's almost 30M. When I changed some items in database, the size of access database changes to 44M. I just changed some text or other fields and didn't add any new item or picture to it. Every time I change the database, the size of database will increase. It seem that it will increase without limit if I continue to change it.

    I know I can get the size of database back by the function of "Compact and Repair Database" in Access, but it would be troublesome.

    Anyone can help me? so I can access the database but not enlarge its size?

    Thanks.

    Bill white
     
  2. Loading...

    Similar Threads Forum Date
    How to prevent sikh erosion? Blogs Oct 21, 2015
    Leisure Stomach Protection / Prevention for travelling to India?? Business, Lifestyle & Leisure Oct 18, 2013
    Controversial Panch Pardhani leader arrested; prevented from attending Shaheedi samagam of Bhai Jaspal Singh Hard Talk Mar 30, 2013
    World Women must play greater role in conflict prevention, UN says Breaking News Oct 28, 2011
    Sikh Coalition Bullying Prevention Summit. Register Today! Sikh Organisations Oct 19, 2011

  3. Tom Wickerath

    Tom Wickerath
    Expand Collapse
    Guest

    Hi Bill,

    I'm not sure why you state that running compact and repair is troublesome,
    other than the amount of time it can take with a database that is 30+ MB.
    This is the only way to reclaim space, after records or objects (tables,
    queries, forms, etc.) have been deleted. In addition, running compact and
    repair on a regular basis will help JET to properly optimize your queries.

    Using OLE Embedding to store images in Access is known to bloat the
    database. Access MVP Larry Linson has some samples that you can download that
    demonstrate how to avoid this bloat. 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.

    Here is a list of KB articles that relate to database bloat:

    http://tinyurl.com/2dmpw


    Tom

    http://www.access.qbuilt.com/html/expert_contributors.html
    __________________________________________

    "Bill White" wrote:

    I am using access database in my app to store text, picture and so on. it's
    almost 30M. When I changed some items in database, the size of access
    database changes to 44M. I just changed some text or other fields and didn't
    add any new item or picture to it. Every time I change the database, the size
    of database will increase. It seem that it will increase without limit if I
    continue to change it.

    I know I can get the size of database back by the function of "Compact and
    Repair Database" in Access, but it would be troublesome.

    Anyone can help me? so I can access the database but not enlarge its size?

    Thanks.

    Bill white
     
  4. Bill White

    Bill White
    Expand Collapse
    Guest

    Tom,

    Thanks a lot.

    Bill White
    "Tom Wickerath" <AOS168 AT @comcast DOT net> wrote in message news:076C6B36-723E-481E-B10B-041D72EE4DA6@microsoft.com...
    Hi Bill,

    I'm not sure why you state that running compact and repair is troublesome,
    other than the amount of time it can take with a database that is 30+ MB.
    This is the only way to reclaim space, after records or objects (tables,
    queries, forms, etc.) have been deleted. In addition, running compact and
    repair on a regular basis will help JET to properly optimize your queries.

    Using OLE Embedding to store images in Access is known to bloat the
    database. Access MVP Larry Linson has some samples that you can download that
    demonstrate how to avoid this bloat. 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.

    Here is a list of KB articles that relate to database bloat:

    http://tinyurl.com/2dmpw


    Tom

    http://www.access.qbuilt.com/html/expert_contributors.html
    __________________________________________

    "Bill White" wrote:

    I am using access database in my app to store text, picture and so on. it's
    almost 30M. When I changed some items in database, the size of access
    database changes to 44M. I just changed some text or other fields and didn't
    add any new item or picture to it. Every time I change the database, the size
    of database will increase. It seem that it will increase without limit if I
    continue to change it.

    I know I can get the size of database back by the function of "Compact and
    Repair Database" in Access, but it would be troublesome.

    Anyone can help me? so I can access the database but not enlarge its size?

    Thanks.

    Bill white
     
Since you're here... we have a small favor to ask...

More people are visiting & reading SPN than ever but far fewer are paying to sustain it. Advertising revenues across the online media have fallen fast. So you can see why we need to ask for your help. Donating to SPN's is vote for free speech, for diversity of opinions, for the right of the people to stand up to religious bigotry. Without any affiliation to any organization, this constant struggle takes a lot of hard work to sustain as we entirely depend on the contributions of our esteemed writers/readers. We do it because we believe our perspective matters – because it might well be your perspective, too... Fund our efforts and together we can keep the world informed about the real Sikh Sikhi Sikhism. If everyone who writes or reads our content, who likes it, helps us to pay for it, our future would be much more secure. Every Contribution Matters, Contribute Generously!

    Become a Supporter      ::     Make a Contribution     



Share This Page