Catherine Blansett
catherine.blansett at infocentraldata.org
Fri Apr 18 07:04:26 CDT 2008
Thank you Dan,
Well, it appears my problem might be solved. At least partially, I still get
a copy of the db when I compact it (original + copy "db1," etc.) IT updated
some of the service packs. I was using Jet 2.x. It appears to be some
better. I noticed on system information regarding Access, Access is still
using Jet 2.x but the ODBC is updated to Jet 4. So, it looks like there
still may be work to do. All comments are welcomed.
Thank you all for your help.
Catherine
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Wednesday, April 09, 2008 8:43 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] ldb
Hi Catherine,
For FE bloating, change the Database format to Access 2000. Then
periodically decompile and compile that access file. If it contains temp
tables, then you could also compact it.
But you won't be able to do any of this while the ldb file exists because
someone else is still logged in!
HTH,
Dan
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Catherine
Blansett
Sent: Wednesday, April 09, 2008 8:25 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] ldb
Thanks Drew, I'll tell them that.
I am not as worried about the backend. It's the frontend that I have the
bloating problem with. I am still doing some development work on it and I
cannot compact it while the ldb file is there. So, it keeps getting bigger.
Catherine
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
Sent: Wednesday, April 09, 2008 10:13 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] ldb
Two things. If compacting the backend is making it smaller, then you
should look at what you are doing with data in the backend.
A database does not automatically free up space when you delete data.
There are several practices that can reduce the amount of 'bloat' to a
database (growth that goes away when you compact the database). One
biggie is if you are using 'temp' tables (where you are writing data
that gets over written frequently), move such processes to the front
end.
The second thing, is your IT folks don't need to reboot the server.
Just use Computer Management and 'close' all the open file connections
to the Backend .mdb.
Drew
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Catherine
Blansett
Sent: Wednesday, April 09, 2008 7:30 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] ldb
Hi all,
I am doing some development work on a research project at a VA medical
center. I have a portion of one drive ("U-drive") and access to a common
drive ("K-drive") for research purposes. I developed a front-end
database
and a back-end database on the "U" drive and put the back-end on the
k-drive. They function as they should. However, while I was developing,
every time I compacted the databases a copy was created and named
db1.....etc.
The original version of the compacted db grew. So, I would rename the
new
version and delete the old (a bit tiring). When I work with these
databases
on my home computer (sans data of course) it works the way it should.
This
situation at work would be bothersome, but doable, if it weren't for the
fact that, at some time (not sure when, but generally, others are
complaining of a slow connection so suspect the system gets bogged
down), it
also creates a locked file that does not allow the databases to be
compacted
- "the db is being used by another", and then gives my ID number. Once
these
databases get locked, it becomes impossible to compact/rename/delete the
databases and to change the name of excel files.
So far, IT is a bit confused. They have rebooted the U drive and this
released the locks and I was able compact, delete, or whatever. But
then, in
a couple of days, I am back to the same situation again. The databases
still
works just fine, but they are getting much too big.
I have heard of this problem, but this is the first time I have
encountered
it. Any help would be most welcomed.
Thanks in advance
CB
No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.519 / Virus Database: 269.22.9/1365 - Release Date:
4/8/2008
7:30 AM
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
The information contained in this transmission is intended only for the
person or entity to which it is addressed and may contain II-VI Proprietary
and/or II-VI Business Sensitive material. If you are not the intended
recipient, please contact the sender immediately and destroy the material in
its entirety, whether electronic or hard copy. You are notified that any
review, retransmission, copying, disclosure, dissemination, or other use of,
or taking of any action in reliance upon this information by persons or
entities other than the intended recipient is prohibited.
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
No virus found in this incoming message.
Checked by AVG.
Version: 7.5.519 / Virus Database: 269.22.10/1367 - Release Date: 4/9/2008
7:10 AM
No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.519 / Virus Database: 269.22.10/1367 - Release Date: 4/9/2008
7:10 AM
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
No virus found in this incoming message.
Checked by AVG.
Version: 7.5.519 / Virus Database: 269.22.10/1367 - Release Date: 4/9/2008
7:10 AM
No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.523 / Virus Database: 269.23.1/1385 - Release Date: 4/18/2008
9:30 AM