[AccessD] Multiple Frontend Users

The last option is basically how you have to do it if you are running on a
thin-client network, something I have often had to do. In this instance a
batch file that copies the 'master' FE to the user's personal network
directory if their copy is out of date works the same way as copying it to
their local machine and is well worth doing. 

Roz
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: 20 May 2008 13:06
To: Access Developers discussion and problem solving
Subject: Re: [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.
>>
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

This e-mail and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments.

Internet communications are not guaranteed to be secure or virus-free.
The Barclays Group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any Internet communications by any third party, or from the transmission of any viruses. Replies to this e-mail may be monitored by the Barclays Group for operational or business reasons.

Any opinion or other information in this e-mail or its attachments that does not relate to the business of the Barclays Group is personal to the sender and is not given or endorsed by the Barclays Group.

Barclays Bank PLC.Registered in England and Wales (registered no. 1026167).
Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom.

Barclays Bank PLC is authorised and regulated by the Financial Services Authority.