[AccessD] Multiple Frontend Users

There is no arguing with the Network Nazis, they own the network and 
what they say goes.  Never mind that it may cause YOU problems.

What you need to at least tell them in a place like that is that the FE 
is transferred to their PC daily.  It is backed up on the network store, 
the local hard drive just makes it faster because there is not so much 
NETWORK TRAFFIC.  Reducing network traffic MIGHT get their attention.

Unfortunately there may be cases where they have just locked the local 
store down and there is nothing you can do about it.  However... each 
user may then get their own NETWORK STORE and you could then transfer a 
copy to their individual network store location and run it from there?

Just things to think about.

John W. Colby
www.ColbyConsulting.com


Arthur Fuller wrote:
> I was presented with this problem recently and recommended this solution.
> The network support people flatly refused it. They argued that in their
> setup (with hundreds of users) virtually nothing on the local PCs was backed
> up. The local PCs can be replaced and/re-imaged anytime, and users are
> warned not to store anything locally, otherwise it won't be backed up. So I
> had no choice but to put both the FE and the BE on a network share. The
> argument makes perfect sense to me, but I've never done it that way before.
> What will happen when a hundred users open a single FE? Should I replace the
> FE MDB with an MDE?
> 
> Thanks,
> Arthur
> 
> On Mon, May 19, 2008 at 10:42 AM, Dan Waters <dwaters at usinternet.com> wrote:
> 
>> Ed,
>>
>> Even with 3 users, splitting is a good preventive measure to avoid data
>> corruption.  You can put the Access Back End .mdb file on the server, and
>> put the Front end .mdb files on each user's PC.  Managing 3 users shouldn't
>> be difficult.
>>