ONE TO ONE DILEMMA

  • Thread starter Thread starter sam1967
  • Start date Start date
S

sam1967

I have been forced to split a table in two for security reasons and it
is giving me a headache.

I find it is easier to enter the firstname and surname in both tables
but realise i am duplicating effort. But it makes it easier tto work
with.

Has anyone ever done this in a ONE-ONE table situation ?
 
I have been forced to split a table in two for security reasons and it
is giving me a headache.

I find it is easier to enter the firstname and surname in both tables
but realise i am duplicating effort. But it makes it easier tto work
with.

Has anyone ever done this in a ONE-ONE table situation ?
Click to expand...

It should never be necessary to enter the same data twice. This is
especially true in a 1 to 1 table. The key should be sufficient to display
the name in both places. If the database has been secured, you should not
find it necessary to require 1 to 1 tables for security reasons alone. You
allow no permissions on the tables and access the data with OwnerAccess
queries so that only those columns which are allowed are seen.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
 
It should never be necessary to enter the same data twice. This is
especially true in a 1 to 1 table. The key should be sufficient to display
the name in both places. If the database has been secured, you should not
find it necessary to require 1 to 1 tables for security reasons alone. You
allow no permissions on the tables and access the data with OwnerAccess
queries so that only those columns which are allowed are seen.
Click to expand...

ah i see. too late for this project i feel. i have already set it all
up with two one-one tables. i will take your advice and ensure that
the name is only entered once in the primary table.
 
Back
Top