dwalker
Technical User
- Nov 29, 2002
- 34
I have a form which imports jpg files and displays them as thumbnails in image controls. 34 images are displayed at any one time, each jpg is about 100k and none of the jpg's are embedded - each is linked and referred to by its path that is stored in a table.
The form's On Current event runs code to find the path for each image control's image and sets the Picture property to that path. Straight forward so far.
After opening the form maybe 20 or so times my database has quickly grown to over 200MB. Remembering that no images are embedded in the database I assumed it just needed compacting but this only reduced it to about 100MB. There are no other objects in the database - one 40-record table and one form with 34 image controls.
I imported the form into an empty database and that new database grew to 100MB. The system table called MSysAccessObjects has over 25,000 records so this is clearly where all the size comes from.
I'm guessing that as a jpg is imported it's probably converted to a bitmap, then all the image data is stored in the aforementioned system table like a type of cache - just a guess but there must be a reason all that data is there.
So, my question is, what can I do to prevent the database getting so big? Can I safely delete data from the MSysAccessObjects system table...?
The form's On Current event runs code to find the path for each image control's image and sets the Picture property to that path. Straight forward so far.
After opening the form maybe 20 or so times my database has quickly grown to over 200MB. Remembering that no images are embedded in the database I assumed it just needed compacting but this only reduced it to about 100MB. There are no other objects in the database - one 40-record table and one form with 34 image controls.
I imported the form into an empty database and that new database grew to 100MB. The system table called MSysAccessObjects has over 25,000 records so this is clearly where all the size comes from.
I'm guessing that as a jpg is imported it's probably converted to a bitmap, then all the image data is stored in the aforementioned system table like a type of cache - just a guess but there must be a reason all that data is there.
So, my question is, what can I do to prevent the database getting so big? Can I safely delete data from the MSysAccessObjects system table...?