Thread: Using Autonumber as PK, cascade update doesn't work?
View Single Post
  #8  
Old March 15th, 2006, 04:24 AM posted to microsoft.public.access.tablesdbdesign
John Vinson
external usenet poster
  
Posts: n/a
Default Using Autonumber as PK, cascade update doesn't work?
On Tue, 14 Mar 2006 18:36:27 -0800, KevinNGC
wrote:

One thing for you John, about a one to one relationship. Other things I've
read lead me to believe that a one to one is one way to implement some
additional security. I'm not sure about what you mentioned, Subclassing and
Table-Based Field Level security yet, still learning as I go here.


We may be talking about the same thing. If you have a table with some
fields which are public knowledge (say an employee's LastName,
FirstName, DepartmentID) and other fields which aren't (CurrentSalary,
PerformanceRating), you can put the latter into a separate table with
a higher level of security.

John W. Vinson[MVP]