Database Distribution - should I installed a front end on every PC?

[kate10123]

Hi there,

I am about to roll out a database to around 8 to 10 users. They have a shared drive where I have placed the back end (hidden file) and front end versions of the database.

Should I also install it on each of these users PCs or will it be ok for each user to access it from one central location?

Any advice appreciated

 

[statsman]

The front end should ONLY be placed on the users computers.

The concept is that if you require security, the back end (the actual data) is protected. Who cares if outsiders can access your reports forms etc. if there is no data contained in them.

If you are going to place both the front and back ends on the same drive, why bother splitting the database?

 

[MSAccessRookie]

The front end should ONLY be placed on the users computers.

The concept is that if you require security, the back end (the actual data) is protected. Who cares if outsiders can access your reports forms etc. if there is no data contained in them.

If you are going to place both the front and back ends on the same drive, why bother splitting the database?

Here are a few other reasons to consider having each user use their own copy of the front end.

• Preventing data corruption - Sharing one front end can lead to data corruption more frequently.
• User identification - Each user has his/her own network ID and the work that they do can be identified if necessary.
• Internal application security - Based on their identification, users can be granted/denied access to functions.

All in all, giving each user their own copy is by far the best way to go if you have more than two users in your group.

 

[kate10123]

Thanks for both replies. I will install it individually then.

 

[The_Doc_Man]

Add one more vote to "local" front-end, "remote" back-end... because everything that is local doesn't have to come across the network. If you have complex forms or reports, the templates can be loaded locally very quickly and the data feed over the network will be your only slowdown. If you had placed the front-end remotely, you would have had to look up the forms, load the templates, and then and only then start downloading the data. (Ditto, of course, with reports.) Also, if you have any code associated with forms or reports (i.e. class modules or general modules), THEY would have to be downloaded if they weren't kept locally.

So it might not be that much, but you are saving the need to load all of your form and report meta-data when you keep that stuff locally.

 

[kate10123]

Thanks, they are all really good points.

I shall make life easier for myself and the users then