Steve Erbach
erbachs at gmail.com
Tue Oct 21 06:53:25 CDT 2014
Brad, I'm sure others will chime in here, but Access isn't a server application. That is, it isn't like, say, SQL Server that is built to provide software services to multiple users and protect each from the others. While an Access front end can work in that environment, the main advantage to installing the front end on each PC is that it reduces network traffic to just the back-end data being retrieved, rather than all forms, reports, and program code, too. Having front ends on each PC does, however, complicate things when it comes to updating your app; but that's a well-known and solved issue. What I'm not sure of is whether having 10 people open the same front end on the network would mean that *all* of them crash if just one does...that's something others here would know better than I. I've simply forgotten! Regards, Steve Erbach Neenah, WI On Mon, Oct 20, 2014 at 2:31 PM, Brad Marks <bradm at blackforestltd.com> wrote: > All, > > I recently built a small inquiry system with Access 2007. > > I am using a "Split" database (data stored in a "_be.accdb" backend file). > > The data is coming from an outside source and the inquiry system will > never update the data. > > Currently all of the users (about 10) share the Accdr (front end) which is > stored on a file server. > > A couple years ago, I built a similar inquiry system and I set things up > so that each user had their own copy of the Front-end Accdr file. > > I am now wondering if this is really necessary. > > Would it be Okay for all users to share the Accdr (front end) which is > stored on the file server? > > Please Keep in mind that no updates are ever done via the font-end. > > Thanks, > Brad > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- Regards, Steve Erbach Neenah, WI http://www.NeenahPolitics.com http://www.TheTownCrank.com