Linking table without duplicating PK

My MDB will not be splitted due to just one department use. It is designed
for HR, and they prefer not to have any chances for users to see the dollar
amounts. But they prefer if possible to have the users input the information
and print out the sheet, so on the HR side, they won't have to input the
information again when they receive the paper copy tuition application. I've
thinking of create another database and link them, but when i link them, the
database doesn't know the person exists and create another PK (EmpID) so this
way i have a duplicate copy...which i dont want....

What I want is , create another database and user opens up, only in Add or
Edit mode whichever is the correct way to do, they fill in the information,
and HR administrator would go in and import the information from the User
Database into HR database without duplicating the entries. Any solutions to
this?

All suggestions are appreciated...
Thanks!

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...esign/200612/1

This is not a reason to not split the database. Even if only one user is
going to use the database, splitting it is always the best thing to do. It
makes it much easier to make modifications to the database when it is split.
There is no difference in the security of the data.

Your plan may work, but will not be very manageable. Your best solution
would be to have one database with Access User Group Security implemented so
that it secures the sensitive information as required.

"accessuser via AccessMonster.com" wrote:

My MDB will not be splitted due to just one department use. It is designed
for HR, and they prefer not to have any chances for users to see the dollar
amounts. But they prefer if possible to have the users input the information
and print out the sheet, so on the HR side, they won't have to input the
information again when they receive the paper copy tuition application. I've
thinking of create another database and link them, but when i link them, the
database doesn't know the person exists and create another PK (EmpID) so this
way i have a duplicate copy...which i dont want....

What I want is , create another database and user opens up, only in Add or
Edit mode whichever is the correct way to do, they fill in the information,
and HR administrator would go in and import the information from the User
Database into HR database without duplicating the entries. Any solutions to
this?

All suggestions are appreciated...
Thanks!

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...esign/200612/1

accessuser via AccessMonster.com wrote:
My MDB will not be splitted due to just one department use. It is designed
for HR, and they prefer not to have any chances for users to see the dollar
amounts. But they prefer if possible to have the users input the information
and print out the sheet, so on the HR side, they won't have to input the
information again when they receive the paper copy tuition application. I've
thinking of create another database and link them, but when i link them, the
database doesn't know the person exists and create another PK (EmpID) so this
way i have a duplicate copy...which i dont want....

What I want is , create another database and user opens up, only in Add or
Edit mode whichever is the correct way to do, they fill in the information,
and HR administrator would go in and import the information from the User
Database into HR database without duplicating the entries. Any solutions to
this?

All suggestions are appreciated...
Thanks!


Who are the "users" here? HR staff, or any employee who wishes to submit
a reimbursement application?

Splitting a database is recommended when more than one person will use
the DB at the same time. Just because it's one department doesn't get
around this -- one department could mean 2, 20, or 200 people hitting
the data.

--
Smartin

I know, but 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.
.. any suggestions for linking database???

Thanks

Smartin wrote:
My MDB will not be splitted due to just one department use. It is designed
for HR, and they prefer not to have any chances for users to see the dollar
[quoted text clipped - 13 lines]
All suggestions are appreciated...
Thanks!

Who are the "users" here? HR staff, or any employee who wishes to submit
a reimbursement application?

Splitting a database is recommended when more than one person will use
the DB at the same time. Just because it's one department doesn't get
around this -- one department could mean 2, 20, or 200 people hitting
the data.


--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...esign/200612/1

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.

--