Can anyone help. I have an access database that a week ago was 98mb in size. I have since replicated the database and allowed several users to Synchronize their data with the database. In just over a week the database has grown to over 300mb. What is causing this? I have tried to Compact the Database (will this work?) but I keep getting an error message that the Database is in Use by Another User (it isn't) so I can't do anything about it. Any suggestions ?
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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
My Access Database is growing out-of-hand
- Thread starter AllyF
- Start date
I've had a sim prob in the past. I got round it by splitting the database up into a front end/back database. (back end being the tables and front end being everything else)
Everyone connected will have to shut down & restart their pc's (to release the ldb-locking-file)
Then make a copy, compact it, then split it up (Tools, addins, database splitter)
Put the backend onto a different part of the network.
The front end (which the users open) will then have 'linked' tables-(in the database window-press F11- the tables will show little arrows next to them)
This should sort it. (p.s. always make a copy of the d/b first in case anything goes wrong!)
Everyone connected will have to shut down & restart their pc's (to release the ldb-locking-file)
Then make a copy, compact it, then split it up (Tools, addins, database splitter)
Put the backend onto a different part of the network.
The front end (which the users open) will then have 'linked' tables-(in the database window-press F11- the tables will show little arrows next to them)
This should sort it. (p.s. always make a copy of the d/b first in case anything goes wrong!)
p.s. If you only want to COMPACT it then get all users to Re-boot (as above) and try again.
If still not work then make a copy, compact that and (as long as no one has the orig d/b open), copy this one over it.
The splitting of a d/b does severely cut down on it's growing size so may be worth trying this on a copied version and if all ok copy it over live one (when no-one using it !)
If still not work then make a copy, compact that and (as long as no one has the orig d/b open), copy this one over it.
The splitting of a d/b does severely cut down on it's growing size so may be worth trying this on a copied version and if all ok copy it over live one (when no-one using it !)
When you replicate an access database, the length of the primary keys etc go thru the roof.
I did the same a couple of months back to try to overcome the uploading times when using linked tables.
I got into problems trying to run the replicated system. The standard VB functions wouldn't compile so I had to return to my linked table system.
What a bummer!
John.
I did the same a couple of months back to try to overcome the uploading times when using linked tables.
I got into problems trying to run the replicated system. The standard VB functions wouldn't compile so I had to return to my linked table system.
What a bummer!
John.
I can add that replication should be avoided if at all possible. It works, but it takes a lot of managing. The suggestion to split into front/back end is the best. If your front end is over-large there are techniques to deal with this. Post again if you want more info and I'll put up an e mail address.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
