multiple front ends

[Guest]

This is more of a "For My Information" question. I've been reading here and
it seems that the consensus in building a multi user app is to distribute the
front end so that each user has their own copy. Why is this necessary?
Presumably (and they way I have created my app) all the front end contains is
queries, forms, reports, macros, modules, and possibly some temp tables No
hard data. What is the harm in putting the front end on the network and
allowing all users to access it from there?

 

[Rick B]

Well, if you do that, then why bother to split it at all?

Sharing the front-end allows coruption and other issues.

You can't modify any of the objects if others have the file open.

It is slower for them to run off the LAN.

Rick B

 

[Joseph Meehan]

This is more of a "For My Information" question. I've been reading
here and it seems that the consensus in building a multi user app is
to distribute the front end so that each user has their own copy.
Why is this necessary? Presumably (and they way I have created my
app) all the front end contains is queries, forms, reports, macros,
modules, and possibly some temp tables No hard data. What is the
harm in putting the front end on the network and allowing all users
to access it from there?

Each person then uses their own front end on their own machine. Most of
the processing is done on their own machine not clashing with processing
from everyone else. Also Access seems to be able to keep everyone straight
better if they all are using their own front end.