[AccessD] Backing Up Access MDB

A.D.:

I wish I were in a position to help. I don't think my databases here at work
have enough concurrency to really test it.

The ideal setup would be:

* Non-production data and server - if you crash it, nothing of value is lost
* A way to simulate heavy concurrency and data updates on the backend, and
to create various conditions:
   > Unresolved Read/Write locks, at Record/Page/Table levels
   > Pending/Committing transactions
   > Transactions being rolled back
   > Cascade Updates/Deletes in progress
   > Deadlocks
* Backing up under these conditions to determine stability
* Reading the backed up tables into another mdb file, and re-applying
relationships to ensure integrity was retained.

That said, lack of such tests doesn't diminish the usefulness of your
utility.

However, you should probably think about inserting a caveat: You should have
exclusive access to the data before you backup. The more users you have, and
the more data gets changed, the more this caveat applies.

Do you have, or have you considered adding these features?

* Use Connection Control to establish exclusive access to the backend
* Use the Jet UserRoster to determine if everyone else is out.
* If there are active users, display the list to aid the DBA in getting
everyone out.
* Once you have exclusive access, you can safely backup.

-Ken

-----Original Message-----
From: A.D.Tejpal [mailto:adtp at touchtelindia.net]
Sent: Tuesday, December 09, 2003 10:59 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Backing Up Access MDB


Ken,

    It would be nice if you are in a position to carry out actual trials so
as to ascertain whether it stands the test of multi-user requirements. I
would be interested to know the outcome. (There has been no problem with
single user mode).

Regards,
A.D.Tejpal