client db increasing in size?

[Ted]

Hi all,

I have a front end db located on our server. Its linked to the back end,
also on the server...same directory. I would prefer to have the front end on
the individual machines but for now we have to keep it on the server. The
front end db is growing rapidly. What could cause the front end db to grow
so fast? all of the data is being put in the back end.

TIA
Ted

 

[Ray C]

If the front end is growing, that means, there is some manipulation of data
somewhere. First of all, check if all the tables are attached to the backend.
If there are some local tables (i.e. not attached), then it is possible that
these tables are being manipulated (i.e. records are being
added/deleted/modified). If it is growing rapidly then there has to be
something affecting this.

Keep in mind that even if some of these local tables are flushed (all
records deleted) the size of the database will not reduce, it will stay the
same size. You will need to compact the database in order for it to go to the
actual size.

Secondly, check if users are adding their own queries, reports, macros, etc.
this will cause the front end to increase as well.

Hope this helps.

Ray

 

[Dale Fye]

Ted,

Keep in mind that if you have multiple users accessing the same front-end,
at the same time, you are setting yourself up for failure.

 

[Ted]

it's temporary. hopefully only for the next week. we have about 15 users
accessing the front end db.

have you had problems with this before?

 

[Ted]

Hi Ray, thanks for the response. All tables are linked. There aren't any
local tables in the front end db. It was compacted yesterday and it
increased from 8 MB to 63 MB in the morning. I did have a corruption in the
back end tho. I repaired it. I hope that will help. Still not sure why the
front end was growing like that. The users don't add any objects and none of
the data is being stored in the front end.

 

[Dale Fye]

Yes,

databases locking up
losing data
database corruption

I generally create a batch file accessed via a shortcut from the users
desktop. The batch file deletes the current copy of the front-end that sits
on the users C: drive, then it copies the current front-end from the server,
then it kicks off the application.

I think Tony Toews has a what he calls a front-end-updater (or something
like that) that is a separate Access application that does pretty much the
same thing as my batch file, but only does the delete and copy when it is
necessary.

--
HTH
Dale

Don''t forget to rate the post if it was helpful!

email address is invalid
Please reply to newsgroup only.

 

[Roger Carlson]

Question is, did it grow to 63MB and then stay fairly constant after that?
Databases need room to work and might grow quickly immediately after
compacting, but then grow slowly or not at all after that. If that's the
case, there's nothing to worry about. That's the size it's supposed to be.

If it continues to grow at that rate, then it's time to look at the code in
the FE. Particularly for code that creates and manipulates recordsets or
querydefs.
--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L

 

[dch3]

I have a .VBS script that I have my users run to start my front end. It
actually kills the .MDE file on their machine and then pulls down the one on
the server. Works like a charm and I don't have to worry about distributing
new versions of the front end. Let me know if you'd like it.

 

[John W. Vinson]

Hi all,

I have a front end db located on our server. Its linked to the back end,
also on the server...same directory. I would prefer to have the front end on
the individual machines but for now we have to keep it on the server. The
front end db is growing rapidly. What could cause the front end db to grow
so fast? all of the data is being put in the back end.

TIA
Ted

Having multiple users share the same frontend will cause this kind of bloat,
along with user conflicts and a very real risk of corruption.

If the frontend *must* be on the server, then each user should have a private
folder with their own copy of the frontend. Sharing a frontend gives you all
of the disadvantages of a split application (slower performance mainly), AND
all of the disadvantages of a single shared database, and none of the
advantages of either!

 

[Ted]

Thank you John...good tips. i appreciate it...

Having multiple users share the same frontend will cause this kind of
bloat,
along with user conflicts and a very real risk of corruption.

If the frontend *must* be on the server, then each user should have a
private
folder with their own copy of the frontend. Sharing a frontend gives you
all
of the disadvantages of a split application (slower performance mainly),
AND
all of the disadvantages of a single shared database, and none of the
advantages of either!

 

[Ted]

thanks...that would be handy. i tried that once before but it didn't work.
does it only pull it down if there are updates?