Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / February 2005

Tip: Looking for answers? Try searching our database.

FE BE question

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Mary M - 22 Feb 2005 14:40 GMT
We want to run FEs from seperate Network Directories. Are there any
drawbacks to running the FEs of a small split DB from Network directories vs
copying the FEs to each computer?

Thanks for any help.
Alex Dybenko - 22 Feb 2005 15:23 GMT
Best - is to run FE from local drive. Copying new FE version to each
computer you can easy automate

Signature

Alex Dybenko (MVP)
http://Alex.Dybenko.com
http://www.PointLtd.com

> We want to run FEs from seperate Network Directories. Are there any
> drawbacks to running the FEs of a small split DB from Network directories
> vs
> copying the FEs to each computer?
>
> Thanks for any help.
Mary M - 22 Feb 2005 15:26 GMT
Thanks for the response. I understand it is best to run it locally,
however, I was wondering if there are any issues I need to be aware of if I
decide to run the FEs from the network? Will it work?
Larry  Linson - 22 Feb 2005 16:07 GMT
> Thanks for the response. I understand it is best to run it locally,
> however, I was wondering if there are any issues I need to be aware of if I
> decide to run the FEs from the network? Will it work?

You significantly increase the chance of corruption of the FE if you have
multiple users logged in at the same time. That usually does not, but could,
cause problems with the BE, as well. Some have run this way for long periods
without corruption, and, suddenly, some apparently un-related system change
leads to regular and frequent corruption.

Additionally, the FE will run much slower because it will still be executed
on the user's machine, but every component that is executed will have to be
fetched across the network rather than from the local hard drive. That not
only slows down your database execution but adds to the network traffic and
may slow other, un-related applications as well.

MVP Tony Toews has an automated front end updater on his site at
http://www.granite.ab.ca/accsmstr.htm and I have an article on an approach
that is not automated, but has worked well for me, at
http://accdevel.tripod.com. Either of these approaches should work without
undue burden, and improve both performance and stability.

 Larry Linson
 Microsoft Access MVP
Immanuel Sibero - 22 Feb 2005 16:22 GMT
Hi Mary,

As Alex pointed out, running the FE locally is best. But you can place the
FE's on network folders and run them from there, as long as each person runs
a separate copy of the FE.

The downside? Can't think of anything except maybe slight performance
penalty at load time.

Immanuel Sibero

> Thanks for the response. I understand it is best to run it locally,
> however, I was wondering if there are any issues I need to be aware of if I
> decide to run the FEs from the network? Will it work?
Tony Toews - 22 Feb 2005 22:39 GMT
>We want to run FEs from seperate Network Directories. Are there any
>drawbacks to running the FEs of a small split DB from Network directories vs
>copying the FEs to each computer?

So long as each user has their own copy of the FE that'll work.  It'll
likely be a bit slower but a client as a TS system setup where they
have retained the individual FEs on the file server.

I specifically created the Auto FE Updater utility so that I could
make changes to the FE MDE as often as I wanted and be quite confident
that the next time someone went to run the app that it would pull in
the latest version.  For more info on the errors or the Auto FE
Updater utility see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the
FE on each PC up to date.

In a Terminal Server or Citrix environment the Auto FE Updater now
supports creating a directory named after the user on a server.  Given
a choice put the FE on the Citrix server to reduce network traffic and
to avoid having to load objects over the network which can be somewhat
sluggish.

Tony
--
Tony Toews, Microsoft Access MVP
  Please respond only in the newsgroups so that others can
read the entire thread of messages.
  Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
david epsom dot com dot au - 24 Feb 2005 23:06 GMT
Most people start with running their small FE files from
a network directory.  They only change to local files if
it gets too big and slow, or if two users overwrite each
others data while sharing the file, or if they have
network problems and the file gets corrupted.

(david)

> We want to run FEs from seperate Network Directories. Are there any
> drawbacks to running the FEs of a small split DB from Network directories
> vs
> copying the FEs to each computer?
>
> Thanks for any help.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.