Why would you need 50 frontends? Want I did in one of my applications for church with over 10,000 members was that I had one frontend and many backends (ex. Finance, events, attendance, facilities, Main, etc.). The tables and queries had a ID field that captured the ID of the authorized user that logged into the frontend. Security for all forms in the frontend was on the employee form that issued their ID and specified their access level (ex. Read/write, Read Only, No Access) to the various forms. You can add an additional field in the table for department so when a new user's record is created, the department can be selected from a drop down. This empowers you filter at login to that user's department and display only the records pertaining to that department. One front end makes it easy to maintain and can simplify the user update process if changes are made. It is simplified because, if you chose to add an auto-Frontend updater to the program, each frontend on the users local machine that is networked to the backend can detect your version table change and prompt the user to click 'Yes' to update the software or select 'No' to cancel.
This method means that if a department wants to add new people, they do so in one place. Remember if you are the admin, the code can be written such you can see everybody and the when the user enters their credentials at login and opens the employee form; they will only see the individuals in their department and can modify access levels, and personal information without your intervention.
Hope this is helpful if you are not too far in your development process.
Gregory
From: AccessDevelopers@yahoogroups.com [mailto:AccessDevelopers@yahoogroups.com] On Behalf Of luvmymelody@yahoo.com
Sent: Monday, September 09, 2013 2:44 PM
To: AccessDevelopers@yahoogroups.com
Subject: [AccessDevelopers] Split Database question
I think that I am a little closer to having another split database scenario here at work. I have been trying to get this for a long time. There is considerable push against this but I found crack in the armor last week.
They asked me if we could split a certain database to 50 or so users. I told them I believe so. The most I have done was 20 databases. The problem is that they see that amount of databases as an issue. I told them that I already have the knowledge and set up already working.
This would be in some respects a nightmare to manage though. It is a Performance Evaluation database for about 500 employees and about 50 supervisors, leads and directors.
Is there an issue with this many databases as front ends? What can I say to convince them? What kind of security can I implement to reduce the amount of databases to have large departments with many different people using the database so others cannot see other supervisors' employees?
Thank You
Jim Wagner
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (2) |
Please zip all files prior to uploading to Files section.
Tidak ada komentar:
Posting Komentar