database increasing in size exponentially

  • Thread starter Thread starter Marcia Schulman
  • Start date Start date
M

Marcia Schulman

I am working with a database thats 16 meg when
compressed. It's on a network with 3 users. After using
it for about 2 hours it increases in size to 586 meg!
Does anyone have any idea how I can remedy this problem?
 
How do I split it into front end & back end?
I do have an image stored that is used as a header in all
the forms. Could that be causing a problem?
Everyone is working with the same file via a shortcut. Is
there an alternative?
 
There is a wizard for splitting the db which is very easy to use.
Tools>>Database Utilities>>Database Splitter

You want to understand the concept before doing this, and make a backup
first as well. What is essentially happening is that you will have tow
databases...one with tables only (Back-end), and the other with everything
else (front-end). The FE will have links to the back-end. Place a copy of
the FE on each user's workstation and the BE on the server (the wizard will
ask where you want the BE to be).

One image shouldn't be a problem.

Your issues are almost certainly related to everyone using the same file.
This is also a great way to corrupt the database.

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/Newsgroups
 
Marcia Schulman said:
I am working with a database thats 16 meg when
compressed. It's on a network with 3 users. After using
it for about 2 hours it increases in size to 586 meg!
Does anyone have any idea how I can remedy this problem?

In addition to the splitting suggestions, which I'd do first. you may
have different Jet versions on computers. Compare the version of
msjet40.dll on the systems.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
How do I split it into front end & back end?

Tools... Database Utilities... Database Splitter. This will create a
new database (with _BE appended to the name of your current database)
containing just the Tables; everything else will remain in the
"frontend" database, linked to the tables. Each user should have a
separate copy of this frontend on their own machine.
I do have an image stored that is used as a header in all
the forms. Could that be causing a problem?

Yes. Access is LOUSY at handling images. If you must do this, keep the
image as small as possible and embed it in the form, rather than
loading it when you open the form.
Everyone is working with the same file via a shortcut. Is
there an alternative?

Yes, the split database above - MUCH preferred.
 
Back
Top