Table Question!

B

Bob V

I have just noticed something about my 2 main tables
tblOwnerInfo,Uses Auto Number as a form of ID
tblHorseID, has No Auto Number
Should I do anything about it.............Thanks Bob
 
P

Pete D.

Disclaimer
At least that is what the release list said, I have only played with 2007
and haven't had or corrected this problem. ;~)
 
J

Jeanette Cunningham

Hi Bob,
There doesn't have to be an autonumber.
There doesn't have to be a Primary Key.

In your tblHorseID is there a field with Indexed property set as
Yes(NoDuplicates)?
If so, then this field is most likely the primary key for tblHorseID.
There can be reasons for using a number or text field for the primary key of
a table instead of an Autonumber, some people like to avoid Autonumber
fields all together.

If your database is working fine as it is, I wouldn't worry about the
tblHorseID.

Jeanette Cunningham
 
J

Jeff Boyce

Bob

Relational database design pretty much requires a unique row identifier for
each table.

Microsoft Access offers an Autonumber data type that pretty much is
guaranteed to be unique, and can be used as a primary key (unique row
identifier).

Is there a primary key already in place on your tblHorse?

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
B

Bob V

oops look at the wrong table , they are both IDs AutoNumber (Increment)
So I suppose that's OK....Regards Bob
 
J

John W. Vinson

I have just noticed something about my 2 main tables
tblOwnerInfo,Uses Auto Number as a form of ID
tblHorseID, has No Auto Number
Should I do anything about it.............Thanks Bob
Click to expand...

What do you see as being a problem?

What is the Primary Key of each table?
How are the tables related?
Does your tblHorseID have *some* field which meets the criteria for a Primary
Key: Unique (only one record in the table has that value), Stable (rarely or
never will the field be edited once it's entered), and Short (Long Integer
Number, or <= 12 bytes text)? If so you don't *need* an Autonumber.

John W. Vinson [MVP]
 
Top