| re: back-end being opened in exclusive mode... how?
When you re-link, one of the options is 'exclusive'. If you
use the wizard, make sure the checkbox is cleared. If you have
DAO code to relink, use 0 (zero) as the relink option instead
of dao.dbAttachExclusive
To prevent exclusive access, open the BE database, goto security,
SCROLL UP from tables TO DATABASE, and remove the exclusive
access permission from the 'admin' user.
(david)
"Chuck Van Den Corput" <NOSPAMcvandencorput@sympatico.ca> wrote in message
news:28h370pqk77q7891lvjfa2okaqjmd93l2v@4ax.com...[color=blue]
> I have encountered a problem that I am hoping someone can shed some
> light on.
>
> I have a multi-user A97 app. All users have a personal front-end MDE
> accessing a shared back-end.
>
> There is no specific MDW file for the app as security rules are housed
> within the app itself.
>
> On a couple of occasions, different users have launched the app only
> to have the back-end opened in exclusive mode, preventing others from
> being able to run the app. The absence of an LDB file precludes the
> use of LDBViewer to ascertain which user has the back-end locked.
>
> Once the user in question had been identified and exited the app,
> multiple users could then launch the app with no problems.
>
> My questions:
> * how can this even happen? (i.e., a front-end causing a back-end to
> be opened in exclusive mode?)
> * is there any way to programatically ensure that a back-end is NOT
> accessed in exclusive mode?
>
> Chuck[/color]
| 
