ldb file

K

Kim

I have a process that will be running that looks for the ldb file for a
database. If the ldb file exists, it is deleted. It is assumed that a user
is not in the database, because this process runs in the middle of the night.
Is there a any problems with this scenario?

Thanks,

Kim
 
K

Kim

The database is being updated at night. A copy of the database is moved from
the network directory to a working directory. Updates are made and the
databse is moved back to the network. The assumption should be correct,
because a function runs that detects user inactivity after 1 hour. After no
user activity, the database closes. I w ould assume the ldb file would be
present if the database was not closed properly. I wouldn't want to copy
over a "suspect" database, make changes and find the copy is corrupted.
 
R

Roger Carlson

Then you've got me badly confused. You said in your original post that if
the LDB is found it is deleted because you assume everyone is out. If
everone HAS to by out, why would there be an LDB file left?

As to the "suspect" database part, I would copy the file to the working
directory twice, once to process and once (other another name of course) to
act as a backup in case something does go wrong.

--
--Roger Carlson
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
 
N

Nick Coe \(UK\)

There can be an ldb file left if the mdb was closed badly,
poor choice of words but I can't think of a better way to
describe it.

As long as you test for the presence of a user or inactivity
then ditch the ldb and backup the mdb (you may have to
jetcomp it first if it closed badly) you are probably ok.
No definates I'm afraid.

--
Nick Coe (UK)
AccHelp v1.01 Application Help File Builder
http://www.alphacos.co.uk/
Download Free Demo Copy
----
 
Top