multi user - position of FE or how to convince the system admin

[Reinier10]

Hi,

At work we're running an acces db that I developed and have to maintain now, with approximately 30 users. Actually it's working quite alright for a month now, but I'm still bothered with the installation for each user and a nobody when it comes to system/hardware configuration.
The problem is, that users (including me) do not have writing priviliges on their local machine's harddrive. Therefore I created a seperate directory on the server for each user, since each user needs his own frontend to avoid corrupting it. I think this is really a 'poor man's' solution, and would like to know if it might cause any problems in the future I am currently unaware of. These would also be good arguments to convince the administrator in helping out (= placing the FE on the local hardrive?) Also, does someone have suggestions on maintainance?
Thanx in advance for any comments,

Reinier

 

[dhookom]

FEs on local hard-drives provide faster form loading. You could even copy some fairly static lookup tables to the FE for even better performance.

I can't believe you don't have some folder on your local hard drives that you can read and write. I work for a large company that locks down our PCs quite tight but you need some place on the local hardware.

Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]

 

[willir]

Reinier

to me, the biggest advantage of using a front end is easier maintenance. With one database used for both the front end and back end, any changes to the forms and reports, etc are made which can compromise the entire database.

There are other advantages including the one you elude to.

I have heard and seen claims that fe/be can improve / deteriate performance. (Even with Autocorrect disabled).

But the best of the best strongly recommend using fe/be...
The Ten Commandments of Access #6

Note that backingup a database is also included in this list. Would your IT Server / Network / Desktop people decide backups are not important? Ditto for splitting up the database.

...Moving on.
Not allowing write-access to C: is common with a standard office / consistant office desktop. This approach greatly reduces the amount of problems with the desktop -- more stability, only approved applications installed, etc. Huge issue, BUT the approach allows on desktop support person to support to manage 150 or 300 seats. Otherwise, you may have to have one It person for every 50 seats. From a management perspective, it makes financial sense (but the opportunity costs, the cost of lost performance is not always considered).

Another benefit for locking down the desktop is security -- huge, huge priority with many corporations, especialy financials and government.

However, you can still use a fe/be...
- The FE can be located on the network, even in the same directory as the BE.
- Many times, users will be given a HOME directory on the network. You should be able to have the BE stored on their HOME directories. With consistant drive mapping, you should be able to apply a consistant approach...

M:\MyData\YourFE.mdb

...where each user has their own M: drive (or L: drive, H: drive, it depends on the standards)

- Don't have a HOME drive. Hmmmm. Then where are the TEMP files and TEMP Internet files stored?? You need a work area with a Windows type of OS. The last approach would be to have the login script copy the FE to the work area.

Richard

 

[Reinier10]

Thank you all for your replies, they cleared up the things I didn't grasp completely.

Yes , (of course) we have access to the local harddrive, but only the mydocuments folder. We also have a HOME drive, I think that is the best place for the FE then. For maintainance I think of a central 'startup' db placed on the server that copies the FE to the users home drive. Start working on it tomorrow.

Grz
Reinier