Re: Pros & Cons of sharing a front end MDB (Client workstation vs. Server)
- From: "Tony Toews [MVP]" <ttoews@xxxxxxxxxxxxxxx>
- Date: Mon, 16 Jul 2007 18:51:15 GMT
Max Vit <mvit@xxxxxxxxxxxxx> wrote:
Common sense tells me that if I have the Front End in the server then
maintenance should be a breeze because you maintain all your forms,
VBA codes, libraries, options, etc in just one place -
Not really. Even if you give each user their own copy of the FE MDB/MDE, which is
what you must do, then you would need to kick each user out before you could give
them a new copy of the FE. PITA.
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.
But it *seems* that in a shared environment it is better to have each
client with a copy of the Front End installed at their workstations
because the LDB file that contains the locking information seems to
work better -
Using a shared copy of the FE risks corrupting the FE. And you might not even be
able to do that as you can get some interestnig messages.
The problems really have nothing to do with the LDB file.
and this would be high maintenance because there are ~50
clients to maintain.
Not with the Auto FE Updater or similar approach. Once setup you can forget about
all the high maintenance details.
Is this correct? Will I have less chance of trouble with LDB files if
I have the Front End living on client's workstations as opposed to
having the Front End living on a server and being accessed by multiple
clients?
Very much so. Now you can put each users FE on the file server. But the
performance would likely be slightly slower.
What would be best practice in a shared environment for a split MDB?
To have the Front End being accessed directly on the server or to
install the Front End on each client's workstation?
Never, ever share a FE MDB/MDE.
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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
.
- Follow-Ups:
- References:
- Prev by Date: Re: Pros & Cons of sharing a front end MDB (Client workstation vs. Server)
- Next by Date: Re: Split a Memo field
- Previous by thread: Re: Pros & Cons of sharing a front end MDB (Client workstation vs. Server)
- Next by thread: Re: Pros & Cons of sharing a front end MDB (Client workstation vs. Server)
- Index(es):
Relevant Pages
|
