Tom,
Thanks a lot.
Bill White
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
__________________________________________
:
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
