Database file has grown 40x bigger, no idea why.

chin chin

Registered User.
Local time
Today, 23:50
Joined
Nov 29, 2010
Messages
40
Hi,

I'm a beginner using Access 2007 and have had some strange problems today. I've been trying out splitting my database and making an accde file, but then decided to recombine the database by importing the modules/forms etc into the b/e. Everything seems to be working ok but for some reason the file has now grown from about 1mb to over 40. No idea what has happened and would appreciate any suggestions.

Thanks alot for any help.

Chin chin.
 
dbs's store lots of temporary objects

compact and repair removes them, so that might hlep.

the other thing that causes bloat is images being imported into a dbs.

----------
you are better keeping the split datbase than combining it - easier to develop in a multi user situation.
 
Thanks for the suggestions - I already tried compact/repair though with no luck. There is a couple of images but only on forms and they were there before the file got massive.

It was my intention to keep it split but it turned out that the lag on the (rather slow) network was irritating so I thought I'd recombine then split again when I was finished.

Chin chin.
 
Thanks for the suggestions - I already tried compact/repair though with no luck. There is a couple of images but only on forms and they were there before the file got massive.

It was my intention to keep it split but it turned out that the lag on the (rather slow) network was irritating so I thought I'd recombine then split again when I was finished.

Chin chin.

Don't recombine and then split again. Just make a copy of the backend and put it on your machine and link to that (using Linked Table Manager) while you are doing development and then link back to the network location when done.
 
Thanks Bob, will do that next time but too late on this occasion. Have you come across the file size changing before btw?

One more question, a little off topic - I had a look at your website and I'm very interested in the fe updaters (I counted three - 2 versions of yours and one on another site). Could you please recommend which one would suit my db best? It will be a 2007 file so no usergroups. Everyone will have access to the network location. Couple of issues though I wasn't sure on were that the be and fe's will be password protected and the users will be clicking a runtime shortcut (well, that's what I'm currently planning anyway).

Thanks,

Chin chin
 
Gemma The Huskey, it turns out you were right about the pictures. Two small pictures that were about 300kb at full size added 20mb to the db then a further 20 after it was run (temp files or something like that I guess?). Must have forgotten when I'd put them in and thought the bloating had occurred way later. Have linked them now instead - what a ridiculous issue!

Thanks a lot,

Chin chin.
 
Yes its a bit strange that Access encourages the use of images inside databases considering it is so woeful in their management.

Its a bit like digital cameras advertisting digital zoom specifications. Ultimately pathetic.

You just wonder if there has been any discussion of this among the MS developers.
 
if you are getting slow performance on a network the most likely reason is not maintaining a permanent connection. you need to either open a form (hidden) or a recordset, and keep it open until the app closes.

otherwise, access has to keep renegotiating the file connection with windows, which gives a disastrous performance hit
 
There is an option in Access Option in the Toolbar to:

Preserve source image format (smaller file size)

This allows jpgs to be handled as jpgs not bitmaps.

Don't may the images too large size as required to fit the control or there abouts.

Simon
 
Simon ... where can this option be found in 2003 and/or 2007?
 
where can this option be found in 2003 and/or 2007?
It is not in 2003 but in 2007 it is under the big round office button, Access Options, Current Database and the last item in the Application Items section.
 

Users who are viewing this thread

Back
Top Bottom