Run Access App. from Network Front End?

[kagard]

Greetings:

I'm developing an application in Access 2010 for about 15-20 users. In
the past, I've loaded an app's front end on each user's machine. In
the current environment, I have to wait for a sys admin to push
updates to the users. This makes bug fixes and small enhancements
slow.

I know multiple users running an app from the same front end on a
network can cause problems. I was wondering, though, if that's true if
each user has their own copy of the front end residing on the network.
That is, instead of installing a copy of the app on each user's
computer, could I store a copy of the front end for each user on the
network and put a shortcut to that file on their desktop?

Other that the initial load time and network traffic (neither of which
is an issue in the current environment), will this create problems? I
could create a script that writes update copies of the front end to
each user's folder, so bug fixes would be very quick. I've already
build in the ability to send messages to users, and to force log them
out of the application when I need to, so I could clear the deck and
update at will.

Am I missing something, or will this work?

TIA
Keith

 

[John Spencer]

I don't see that your proposed solution will cause any big problems. It
should be a trifle slower.

Personally, I would prefer having the front-end reside on the individual
computers. I would probably put up with the installation delay.

If the users don't complain to the sys admin about the problem, then things
won't change. Even if they do complain, things might not change.

John Spencer
Access MVP 2002-2005, 2007-2010
The Hilltop Institute
University of Maryland Baltimore County

 

[John W. Vinson]

could I store a copy of the front end for each user on the
network and put a shortcut to that file on their desktop?

Several of my clients use this configuration (connecting to individual
frontends over Citrix or over a wired network). It does increase network
traffic a bit but seems to work fine.
--

John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://social.msdn.microsoft.com/Forums/en-US/accessdev/
http://social.answers.microsoft.com/Forums/en-US/addbuz/
and see also http://www.utteraccess.com

 

[kagard]

Thanks, gentlemen - I'll give it a go.

Keith

 

[Tony Toews]

I know multiple users running an app from the same front end on a
network can cause problems. I was wondering, though, if that's true if
each user has their own copy of the front end residing on the network.
That is, instead of installing a copy of the app on each user's
computer, could I store a copy of the front end for each user on the
network and put a shortcut to that file on their desktop?

Yes, that works. As others have said it's a bit slower but might not
even be noticable. A client was doing exactly that in about 2002 on
a Citrix server farm.

Note that the Auto FE Updater will also do the above task and a lot
more. However it's no longer free.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/

 

[a a r o n . k e m p f]

I don't think that Jet is reliable enough for that many users. Sorry.
Upsize to SQL Server and Choose Client / Server application (Access
Data Project)