Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Closing another mdb application

Status
Not open for further replies.

nickperez22

Technical User
Jun 13, 2001
62
US
I need to make sure another frontend application is closed before commencing to do a compact and backup of my database backend data. The front end where I have my backup routine is called VC.mdb and the front end that I want to make sure is closed is called SMP.mdb. So how do I close SMP.mdb from VC.mdb?

 
Did you mean,

"... called VC.mdb and the BACK end that I want to make sure is closed ..."

If so, back ends close automatically, once all Bound forms are closed, and I imagine, All recordsets are Cleaned up.
So from an unbound form, you can call your BackUpDatabase Method.

If you're not talking about a split database then, I, personally, will need time to look it up....

 
The back end is a third database. I have 2 different front end applications that link to the backend. When I do a backup of the backend I want to make sure that the other front end application isn't open.
 
nickperez22,

If there is no ldb file of the other FE, then the other FE is not open. Also if there is no ldb file for the BE you have the chance to start compacting. During that time, no one can open BE or read from any FE.

In case there is no user-level security (so no ldb file anywhere), you could open a connection to the other FE with Exclusive rights. If you succeed then, BE is all yours.
 
I understand all of that, however I come back to my origial question I just need the code in my front end A to be able to shut down front end B in case it is open before the backup process begins of the back end.

This is an application that is in 30 locations and the backup process is working fine however I have noticed during my own tinkering around that under certain cicumstances I can lock up the back end db from the other front end and then the backup process does not run properly. I haven't had any complaints from my users yet, since Front End A currently gives the users a warning message that Front End B should be shut down, this is more a preventative medicine.




 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top