Bloating on Front end of Split Access App

[Guest]

Hi,

I have a Split access application deployed to 30 - 35 seperate facilities.
Each facility has the back end on a file server and the front end on the
users desktop. At one facility the front end of the application bloats from
25 mb to almost 1 gb in a short time frame. I dont know why, I can't see any
corrupt data on the back end. Any clues to look for would be greatly
appreciated.

 

[(PeteCresswell)]

Per Amill:

Hi,

I have a Split access application deployed to 30 - 35 seperate facilities.
Each facility has the back end on a file server and the front end on the
users desktop. At one facility the front end of the application bloats from
25 mb to almost 1 gb in a short time frame. I dont know why, I can't see any
corrupt data on the back end. Any clues to look for would be greatly
appreciated.

My biggest app continues to grow slowly in use. I've remedied some of the
causes, but it seems like there are factors at work that I have not discovered
yet.

What I've discovered so far:
-------------------------------------------------------------------------------
1) Users are changing print setup on reports.
Each change grows the app DB a little.

2) Some process is creating a temp table in the app instead of a
separate work DB.

3) Not closing Query and Recordset objects and then setting them to Nothing.
In a iterative process that keeps re-populating the same RS, for instance,
the DB can grow by about 4k on every loop unless the RS is properly closed
and the pointer destroyed.

 

[PC Datasheet]

AccessXP has a Compact At Close option at Tools - Options - General. Is it
possible that that one frontend does not have it checked while all the
others do?

 

[Guest]

Hi Amill,

In addition to the suggestions that you've already received from Pete
Cresswell and Steve Santus (PC Datasheet), here is a link to a bunch of KB
articles that deal with JET database bloat:

http://tinyurl.com/2dmpw


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

Hi,

I have a Split access application deployed to 30 - 35 seperate facilities.
Each facility has the back end on a file server and the front end on the
users desktop. At one facility the front end of the application bloats from
25 mb to almost 1 gb in a short time frame. I dont know why, I can't see any
corrupt data on the back end. Any clues to look for would be greatly
appreciated.

 

[StopThisAdvertising]

PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
Over 1100 users have come to me from the newsgroups requesting help
(e-mail address removed)

--
To the original poster:

Most people here have a common belief that the newsgroups are for *free exchange of information*.
But Steve is a notorious job hunter in these groups, always trying to sell his services.

Before you intend to do business with him look at:
http://home.tiscali.nl/arracom/whoissteve.html (updated)

Arno R

 

[Tony Toews]

Hi,

I have a Split access application deployed to 30 - 35 seperate facilities.
Each facility has the back end on a file server and the front end on the
users desktop. At one facility the front end of the application bloats from
25 mb to almost 1 gb in a short time frame. I dont know why, I can't see any
corrupt data on the back end. Any clues to look for would be greatly
appreciated.

I'm wondering if somehow, despite what you've stated, that the
bloating FE is being shared by multiple users.

Are you using temporary tables in your FE? Are the users doing
something unusual there such as running operations that use some
temporary tables in your FE a lot.

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

 

[Larry Kahm]

Amill,

Are you, by any chance, using a product from FMS called "Total Access Admin"
to remotely administer the database?

If so, please contact their tech support group and request the latest update
to the product.

I was working at a client site several months ago and ran across a similar
problem. An older version of their code would run on a timer pop and create
a temporary object (in the FE) and even though it was deleted, there was a
tremendous increase in the FE's size. They listened to my problem
description, tried it out, tested it in a variety of circumstances, and were
able to issue a fix rather quickly.

If you are not running this product, something similar probably >is<
occurring in your database.

Larry Kahm
Heliotropic Systems, Inc.