[AccessD] Multiple Frontend Users

 >Isn't most
 > of the traffic fetching data from the back end?

Whenever you load ANYTHING out of the FE it has to be loaded out of the 
container.  Load a form, pull data (the form) from the FE container. 
Load a report, pull data from the container.  Load a query, pull it from 
the container.  Load a module, pull it from the container.  The ONLY 
thing not loaded every time it is opened is the module.  I have never 
seen any actual statistics as to how much data the form / report / query 
itself requires just to load.

Thus there is a fair bit of network traffic just loading the forms and 
reports themselves, never mind the data loaded into the form or report.

John W. Colby
www.ColbyConsulting.com


Heenan, Lambert wrote:
> There's no law that says the FE has to be on the user's local hard drive.
> Most networks I've come across users have their own personal network
> storage, a 'home' drive. I just give them a copy of the FE that runs off
> that network drive. Like Jim Dettman I use a version table and have an
> automated update process.
> 
> (Whisper it: network load be damned). Anyway I don't quite follow the logic
> of the claim that the FE on the C drive reduces network traffic. Isn't most
> of the traffic fetching data from the back end?
> 
> Lambert
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
> Sent: Tuesday, May 20, 2008 7:53 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Multiple Frontend Users
> 
> 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