[AccessD] ldb

Hi Catherine,

I do have the same problem with one customer.  I connect to them via VPN,
which is a slow connection.  I also get the db1.mdb file every time, but I
haven't created any lockouts.

If you have a lockout, first be sure that no instances of Access are
running.  Go into task manager under Processes.  At the bottom, check 'Show
processes from all users.  If you see any instances of Access running (after
being sure that no one is legitimately running Access), end that process.
Then try to delete the .ldb file.

Also, if you (and everyone else) have closed all Office applications and you
see a file called DW20.exe in the Processes tab, end that process.  This is
Microsoft's application which reports data on crashes.  I found once that
ending that process on the server solved problems similar to yours.

To help compacting, you could copy the BE file to the U drive, compact it,
and then copy it back.  That's what I do now as needed.

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 7:29 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