I created a Front end for one of my more popular tools and published the Front End in Citrix. I've never checked to see how many concurrent users Access ends up supporting when I do this. But food for thought.
From: AccessDevelopers@yahoogroups.com [mailto:AccessDevelopers@yahoogroups.com] On Behalf Of Jim Wagner
Sent: Tuesday, September 10, 2013 11:01 AM
To: AccessDevelopers@yahoogroups.com
Subject: Re: [AccessDevelopers] Split Database question
Duane,
That probably will not happen. I have tried to get SQL as part of the environment and it took me 7 years just to have SQL Management studio express installed on my machine. Server space would be another issue. Not sure if anyone wants to do that. I have tried before. Our 2 person department does not get the respect and tools it needs to move forward. I will ask again if there is a space for us to try it.
Jim Wagner
From: Duane Hookom <duanehookom@hotmail.com>
To: access developers <accessdevelopers@yahoogroups.com>
Sent: Tuesday, September 10, 2013 7:23 AM
Subject: RE: [AccessDevelopers] Split Database question
"under FERPA and HIPAA rules" I wouldn't be using Access as a back-end database for this. I would be using SQL Server (or similar) with a locked down front-end.
Duane Hookom MVP
MS Access
________________________________
> To: AccessDevelopers@yahoogroups.com
> From: luvmymelody@yahoo.com
> Date: Tue, 10 Sep 2013 07:07:15 -0700
> Subject: Re: [AccessDevelopers] Split Database question
>
>
>
> Duane,
>
> Yes I meant 50 copies of the same front end. The nightmare would be
> mostly the maintaining the "reports to" piece of the project. Changes
> happen and we are not always informed of changes. I think the biggest
> issue that upper management have is the security part. They do not want
> other supervisors to see other supervisors employee evaluations. We had
> discussed that when the evaluation has been completed, printed, signed
> and delivered that the eval would be archived to another table where it
> is not available to users.
>
> We already have a similar set up where I send the daily updated tables
> to the front ends after the main table is filtered by department and
> then copied to each of the databases. There are no linked tables at all
> because of the paranoia of someone seeing the wrong data. Because this
> is a university and are under FERPA and HIPAA rules, a sense of
> security is a major obstacle to getting some things done even when some
> data is already know by all.
>
> Jim Wagner
> ________________________________
>
> ________________________________
> From: Duane Hookom <duanehookom@hotmail.com>
> To: access developers <accessdevelopers@yahoogroups.com>
> Sent: Monday, September 9, 2013 2:31 PM
> Subject: RE: [AccessDevelopers] Split Database question
>
>
> 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
This email (and all attachments) is for the sole use of the intended recipient(s) and may contain privileged and/or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (7) |
Please zip all files prior to uploading to Files section.
Tidak ada komentar:
Posting Komentar