I'm with Bob. I'd put all the objects into one database front end. The back end probably should be in SQL Server due to PPI and FINI. Setting up user groups will give you the ability to filter everything as needed. Of course that means a User table, too, so you can determine the user's group.
---In MS_Access_Professionals@yahoogroups.com, <bob@alternatefinishing.com> wrote :
Sounds like a case that needs to have user-groups. Each group only sees the reports and forms that they need / want to see.
Bob Peterson
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Tuesday, October 27, 2015 6:20 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Database Administration question
Hello all,
Because we work for a University, we are under Federal and State laws that pertain to data. With FERPA and HIPPA as several restrictions of data and who can see it.
We support over 50 databases that have both financial and HR data. Some databases were here before my boss and I came over 12 years ago. The databases are diversified by departments and purposes.
But there are some objects such as reports, queries and tables that are found across the varied databases. There is even a process that is in 2 databases, that is exactly the same. My boss and I are talking again about the duplicated maintenance and development we need to do. 99% of the reason for the scenario is that someone was paranoid about security(see first paragraph). Even though everyone can see the data through the Enterprise PeopleSoft application.
We have reports with the same source but someone does not wan t to see a certain field. Someone thinks that a certain field is too sensitive, We even have a database with the 17 reports with the same data that has different criteria for each report. Because someone did not want to filter the report. It is crazy working here. My boss said no more duplicate work, yet we are tied to the requests of the users.
My boss wanted me to ask if this is normal business practices at other places? Are we allowing this free for all? Do other developers go through this also? Is there something we can do to curb another report based on the same data.
I created several years ago a repurpose database that has some objects processed and then copied to the respective databases to prevent this behavior and work. Yet we are still stuck on this trend of creating similar objects in many databases.
So the question. What are other developers doing to prevent duplicate work like this?
Thank Yo u
Jim Wagner
Posted by: wrmosca@comcast.net
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (3) |
Tidak ada komentar:
Posting Komentar