How to avoid another instance of an app

[GraeagleBill]

I've run into a problem with a user that opens an Access app, performs several actions, that might or might not involve a data update, suspends actions and moves off to several other Windows based apps, browser, mail etc.. Then when wanting to return to the Access app launches a 2nd instance of the same Access app. While the app error handlers deal with DB conflicts appropriately, the user is unsophisticated to an extent that problems encountered persist. So, I need an approach the includes detection of the already running app and the VBA to re-activate the initial instance.

I can look to see if the app has an "ldb" file of itself, but if so how does one reactivate the app associated with the "ldb"? NOTE: there could be other Access Applications running, so it does not suffice to simply look for the Access Application. That is, code like inserted here wouldn't work:

Dim objX As Access.Application

Set objX = GetObject(, "Access.Application")

If Not objX Is Nothing Then
MsgBox "MS Access is already open!"
End If

Thanks,
Bill

[Micron]

Not foolproof but why not just log them in in the user table. Surely you have one by now?
There should be nothing wrong with opening multiple instances of Access (assuming they actually have the full program), just not multiple sessions by the same user in the same db?
One issue with logging in is that some people will go to any length to exit abnormally, even to the point of pulling the plug (literally). Those (ahem) miscreants will have to either
a) get a message that they're already logged in and thus resume the existing app
b) be caught doing an abnormal shutdown and requiring an admin to remove their login flag (whatever that may be), upon which after the 2nd time they are summarily hung by their eyelids and beaten until they blink.

[CJ_London]

I've only had to do this for one client.

I have the app check if user is already logged in (a login table) and if so exits with a message, 'app already open'

If the user has exited illegally (i.e. without closing the app properly and logging out) then they run another app which takes them through the hoops to logout. My client insisted this process should take a few minutes and asks for all sorts of irrelevant information (security questions if you like) to emphasise to the user the error of their ways. Just unfortunate if the close was by accident (powercut whatever)

[wvmitchell]

You could change Access to open Exclusive, instead of Shared which is the default. In that way, if they try to open another instance it will stop them.