When it came time to deploy our Access 2K application we decided to use a .mde format because it was my understanding that they cannot grow in size the way that a .mdb often does. However, we have recently discovered that the .mde files on the users' PCs is growing in size as it is used. In some cases the file grew to twice the original size. Several of the users have experienced errors and crashes when the file size goes over 100mb. I know I can fix this problem by turning on the Compact on Close feature but I still can't explain how this is happening. Does anyone know how it is possible that a .mde file could be growing in size? I'm having trouble finding resources on this subject. Thanks for you help!
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Application .mde growing in file size 1
- Thread starter Orion45
- Start date
-
1
- #2
Dear Orion45,
Well, even though you have defined a frontend / backend solution (Note: good for you, that is the correct way to develop an access application), whenever you run a query or add records to a local table, your 'mde' will grow a little to store that information while you are using it.
So, mde's will also grow in size unless you compact. The good thing, if the mde ever get's corrupt, you can just copy another mde or make an access mde from the source program.
Hope This Helps,
Hap![[2thumbsup]](/data/assets/smilies/2thumbsup.gif "[2thumbsup] [2thumbsup]")
Access Developer![[pc]](/data/assets/smilies/pc.gif "[pc] [pc]")
Access based Add-on Solutions
Access Developer Forum
xx
Well, even though you have defined a frontend / backend solution (Note: good for you, that is the correct way to develop an access application), whenever you run a query or add records to a local table, your 'mde' will grow a little to store that information while you are using it.
So, mde's will also grow in size unless you compact. The good thing, if the mde ever get's corrupt, you can just copy another mde or make an access mde from the source program.
Hope This Helps,
Hap
Access Developer
Access based Add-on SolutionsAccess Developer Forum
xx
- Thread starter
- #3
Thanks for your response. I do understand what you're saying about Access saving temporary records but I'm not sure that is the case here. The majority of my application does not use linked tables or Jet SQL. I am able to bypass this by using ADO recordsets to create, read, update, and delete tables directly on my SQL Server backend. I always make sure to close recordsets after I'm done with them so I'm not sure how the file size increases. Is there an aspect to this I'm just not seeing? Thanks again for your input.
I realize that the work is being handled by SQL and ADO, but access creates its own work areas to process records that are returned. The actual record sets that ADO Creates need to be in Access's db to use. Think of it as the same concept as windows uses when it does memory swapping. It is just a temp area that grows. The reason it grows (basically a guess here) is that access does not delete temp work areas unless told to do so, thus the compact feature is needed. That is why a frontend can grow quite large and there is a huge saving when compacted, but the backend, where the data is stored, does not see the same reduction in size (Percentage) unless you add and then delete many records.
Hope This Helps,
Hap
Access Developer Access based Add-on Solutions
Access Developer Forum
xx
Hope This Helps,
Hap
Access Developer
Access based Add-on SolutionsAccess Developer Forum
xx
- Thread starter
- #5
Dear Orion,
Why not have the compact feature be run once a week?
You could have an Access program (different then your App) as the starting Application. Then, say on Fridays, this little startup application would compact the program before running the main Application. Or, if you used this method, you could ask the user first.
Finally, you could place two startup shortcuts on the user's PC. One would run the program and the other would compact the program. Then just educate your users to run the compact once in a while.
Good Luck,
Hap...
Access Developer Access based Add-on Solutions
Access Developer Forum
xx
Why not have the compact feature be run once a week?
You could have an Access program (different then your App) as the starting Application. Then, say on Fridays, this little startup application would compact the program before running the main Application. Or, if you used this method, you could ask the user first.
Finally, you could place two startup shortcuts on the user's PC. One would run the program and the other would compact the program. Then just educate your users to run the compact once in a while.
Good Luck,
Hap...
Access Developer
Access based Add-on SolutionsAccess Developer Forum
xx
Dear Orion,
I found another solution to your compact on exit in a FAQ on Tek-Tips.
Check this out:
Auto Compact your Database when FileSize = x
faq705-2852
Later,
Hap...
Access Developer Access based Add-on Solutions
Access Developer Forum
xx
I found another solution to your compact on exit in a FAQ on Tek-Tips.
Check this out:
Auto Compact your Database when FileSize = x
faq705-2852
Later,
Hap...
Access Developer
Access based Add-on SolutionsAccess Developer Forum
xx
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question