separate front ends

[rebeccax]

In a multi-user environment, what is the advantage of having a front end for
each user, rather than a single front end that they each point to?

 

[Dirk Goldgar]

In a multi-user environment, what is the advantage of having a front end
for
each user, rather than a single front end that they each point to?

1. If the front-end is shared across the network, there is much greater
exposure to corruption.

2. If one user's front-end becomes damaged or corrupted, other users aren't
affected.

3. From a designer's point of view, it's possible to put user-specific
tables in the front-end.

4. Each front-end can be configured for a specific user's preferences, if
desired.

5. Updates to the front-end can be rolled out user by user, rather than
having to kick all users out.

There are probably others I cant think of at the moment.

 

[John W. Vinson]

In a multi-user environment, what is the advantage of having a front end for
each user, rather than a single front end that they each point to?

The shared frontend will suffer user contention, rapid bloat, poor
performance, and a greatly increased risk of corruption; and you'll get none
of the advantages of a split database.

 

[rebeccax]

Dirk,

Thanks for the info. I suppose I've been lucky in that I've never had
problems with corruption. In the past I've controlled who has permission to
what with security groups and retrieving network names, etc.

If you could say more about configuring for specific user preferences I'd
appreciate it. And not having to kick all users out is a huge plus.

Regards,
Rebecca

:

 

[Tony Toews [MVP]]

In a multi-user environment, what is the advantage of having a front end for
each user, rather than a single front end that they each point to?

For more reasons see the "Splitting your app into a front end and back
end Tips" page at http://www.granite.ab.ca/access/splitapp/. Although
you've already split it.

See the free Auto FE Updater utility at http://www.autofeupdater.com/
to make the distribution of new FEs relatively painless.. The
utility also supports Terminal Server/Citrix quite nicely.

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/
Granite Fleet Manager http://www.granitefleet.com/

 

[Tom Wickerath]

As others have already pointed out, you are not getting the full benefits of
splitting by sharing a common FE file. Here are two more links that contain
useful information on the topic of splitting:

Split the Database
http://www.access.qbuilt.com/html/gem_tips1.html#SplitDB
http://www.accessmvp.com/JConrad/accessjunkie/splitting.html


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
__________________________________________