Re: Linking table without duplicating PK
- From: "Jamie Collins" <jamiecollins@xxxxxxxxxx>
- Date: 20 Dec 2006 02:11:44 -0800
On Dec 20, 1:17 am, "accessuser via AccessMonster.com" <u28669@uwe>
wrote:
the problem is HR does not want the employees to even go into
this program. I understand by spliting it, limits their access, set
passwords, but all those can still be hacked if those people know how to use
Access. HR does not want to take those chances. I don't want to promise them
that it is totally safe when it is not......So I need to look for alternative.
It's a matter of trust, then.
Do HR trust network permissions i.e. can the two applications reside on
the same network? If so, you may be able to convince them that two
applications can share safely share the same database. However, IMO the
security in Access/Jet is inadequate for the required task. Consider
something more 'industrial strength.' e.g. security in SQL Server is
excellent, even in the free versions (MSDE 2000, SQL Server 2005
Express).
Data integrity is also an important and will be more easily achieved if
the data resides in the same database.
Jamie.
--
.
- References:
- Linking table without duplicating PK
- From: accessuser via AccessMonster.com
- Re: Linking table without duplicating PK
- From: Smartin
- Re: Linking table without duplicating PK
- From: accessuser via AccessMonster.com
- Linking table without duplicating PK
- Prev by Date: Re: Instructor evaluation database
- Next by Date: Re: Database Design
- Previous by thread: Re: Linking table without duplicating PK
- Next by thread: Re: Instructor evaluation database
- Index(es):
Relevant Pages
|
Loading