Pros & Cons of sharing a front end MDB (Client workstation vs. Server)

I have deployed few Access apps splitting it in Front End and Back
End. Our environment uses Win XP SP2 for clients, Win 2k3 for servers
and Access 2003. The max. number of clients is about 50 (concurrent
users is estimated around 10).

Whilst the Back End always lives on a server, I am not quite clear
where the Front End should live.

I have searched the web and find contradicting views.

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 - but I am not
quite clear about *what* Access features are managed on the server and
*what* are managed (and dependent) on the workstation's install of
Access.

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 - and this would be high maintenance because there are ~50
clients to maintain.

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?

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?

.

Relevant Pages

  • Re: Sudden Issues with DHCP & Remote Access
    ... function and when i went to run the wizard, found that the server could not ... In one fix there were instructions to change the path of the clientapps ... then re-run CEICW and reboot the workstations. ... will be assigned to dial in clients. ...
    (microsoft.public.windows.server.sbs)
  • Re: 5 access 2000 users and 1 AccessXP user
    ... Access database in question is in Access 2000). ... The back end is on a server running win2K server. ... Check the permissions of the folder where the workstations are connected ... >> started upgrading my win2K clients to XP and the server is still running ...
    (microsoft.public.access.conversion)
  • Re: Linux - SAMBA/OpenLDAP/Plone/OpenExchange
    ... There is a drastic difference between Windows environment ... adminstration and Unix (Linux mimics Unix, but its close enough to be ... appropriate configuration file to the new server, ... but what I have done in MS world is make my clients ...
    (alt.os.linux)
  • Re: 5 access 2000 users and 1 AccessXP user
    ... Check the permissions of the folder where the workstations are connected ... > I, too, have a split database with the backend on a server. ... > started upgrading my win2K clients to XP and the server is still running ...
    (microsoft.public.access.conversion)
  • Re: 5 access 2000 users and 1 AccessXP user
    ... Using Windows Explorer, locate the front end mdb file on the workstation. ... Check the permissions of the folder where the workstations are connected ... >> I, too, have a split database with the backend on a server. ... >> started upgrading my win2K clients to XP and the server is still running ...
    (microsoft.public.access.conversion)
Loading