Open frontend exclusive ?

[Guest]

Since each user should be running their own frontend in a split db scenario,
is it reasonable to set up the frontends as "open exclusive"?
TIA,
Charlie

 

[Douglas J. Steele]

I don't see that it'll make any difference.

 

[Guest]

Maybe I don't understand "open exclusive" but I thought it meant "one user
only", i.e. if I try to open the frontend app and someone else already has it
open, that my open attempt will fail. Our situation is that we have 4
laptops used by 15 different people so we have 4 frontends, one for each
laptop (each frontend has a single table in the frontend identifying the
location of the laptop). I planned to use the "startup" feature of RDP to
select the frontend but I can't seem to get that to work, so we have 4 icons
on each desktop, thinking the user would know which hotel he/she was in,
BUT.................

If I understand "open exclusive", this would ensure that a specific frontend
could only be used by one person..............hmm?

Thanks for the help,
Charlie

 

[Douglas J. Steele]

In your original post, you seemed to be saying that each user would have
his/her own copy of the front-end database. In that case, since each user
would have the front-end database on their hard drive, it wouldn't be any
advantage to opening exclusively or not.

Is there no way to identify the hotel through your program? Is there a logon
script that maps drives, so that if you knew where a particular drive letter
was mapped, you could identify the hotel? (See
http://www.mvps.org/access/api/api0003.htm at "The Access Web" for how to
determine the UNC for a mapped drive)