2 big problems

  • Thread starter Thread starter hin87_at_yahoo.com
  • Start date Start date
H

hin87_at_yahoo.com

Hi

In Access 2002, the size of my front-end database increases from 5MB
to 56MB over the course of the day. I could see the database size
increases each time I open up reports in Access. My reports use
regular objects like combos, texts and labels. The report does have
linked picture object for my logo (size at 185KB). I'm using a saved
query to grab the data for the reports. It seem like Access do not
want to release the memory after I closed Forms/Reports.

Did anybody notice this big bug in Access? How can I reduce the size
of the files over time, besides doing a Compact database?


Another problem I keep encountering is that my Access keeps crashing.
I would get a message about "Access has just recover from a serious
crash, do you want to send the log file to Microsoft" or sometime no
error message, it would just exit out of MS Access.


Thanks a million,
H
 
Front End implies multiuser. Is this so? If yes, does every user have their
own copy of the front end, or do you have one common copy for all on a
network drive? The latter would explain both your problems. If that's the
case, then distribute a local copy of the FE to each user. See the multiuser
group for more on the subject.

HTH,
Nikos
 
Currently, I am the only user using this database. I am about 90%
complete, so I am the only one working on it. Here is how I structure
the files:

Front-End database: is an mdb file. Will be converting it to mde
after I finish with all the designs. This file contains reports,
queries, forms, and couple of tables.

Back-End database: is an mdb file. This only contains tables.

So your answer didn't really answer my questions.

Thanks,
 
I trick I use:
Put the logo on a SubReport by itself... then it will only be loaded once
instead of once per page
(I discovered that one trying to print 6000+ pages in good old access 2.0
.... well, I got a trip to singapore to fix it - so who's complaining )
I also seem to remember an old Ken Getz article in VB advisor to that effect

HTH

Pieter
 
Back
Top