Jim,
Isn't there just one front-end (master) and one back-end? I assume you mean 50 copies of the same front-end on user's PCs or shares. This should certainly be more reliable than having multiple users opening the same combined file.
I'm not sure why the nightmare unless there is something about the setup that you are telling us.
Duane Hookom MVP
MS Access
________________________________
> To: AccessDevelopers@yahoogroups.com
> From: luvmymelody@yahoo.com
> Date: Mon, 9 Sep 2013 12:43:41 -0700
> 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 (3) |
Please zip all files prior to uploading to Files section.
Tidak ada komentar:
Posting Komentar