Re: Does each related table have to have their own primary key ass

Tech-Archive recommends: Speed Up your PC by fixing your registry

new2datamgmnt wrote:
> I will go into each of them and set an autonumber for the primary key.
>
> However, by adding the primary keys does this by its very nature
> mandate I perform other functions in the forms, queries and reports I
> have already set up so as not to compromise the integrity of the
> newly updated database? If the answer is yes, if you could kindly
> walk me thru the steps of the update required for the forms, queries
> and reports.

If the PK you added had not been an AutoNumber then you would need to modify
your forms so that the PK field is populated when new records are added. Since
an AutoNumber is self-populating then you should not have to do anything.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com


.

Relevant Pages

  • Re: Multi-Field Primary Key
    ... Surrogate numeric keys do solve a lot of technical ... problems for database and database application developers and many seasoned ... I recognise *three* uses for autonumber. ... "Although a primary key isn't required, ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Concatenate and Null Values -- Features
    ... Tony Toews dislikes cascade deletes as well as cascade updates, ... fence regarding the use of natural versus surrogate (autonumber) keys. ... Database Normalization Tips ... For optimal database design and performance, the primary key of a table ...
    (microsoft.public.access.reports)
  • Re: must be a join or relationship problem
    ... created queries and then reports based on those queries. ... Primary Key: ProductID - autonumber ... TableName: Suppliers ...
    (microsoft.public.access.reports)
  • Re: Autonumber Fields
    ... this special meaning is clustered index. ... believe that a clustered index is a requirement for a primary key. ... questions don't understand the purpose of an autonumber primary key. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Does each related table have to have their own primary key ass
    ... I agree with Rick Brandt to some extent, and I can't think of any real problems that you might encounter by adding Autonumber fields that you never use, so you perhaps should go ahead and stick them in there and nothing will go wrong, although they will make your Tables slightly larger and require you to name them and keep track of them. ... one such reason for ensuring that all the records are easily distinguishable (by having a unique primary key field in each record) might be that the Table is part of a self-join. ... The reason I ask is that when I was 1st setting up my database I had the 1st table set with a primary key I assigned (policy #) and I set the next table with an autonumber, but I was getting error messages when I was trying to do reports and forms extrapulating data from both tables. ...
    (microsoft.public.access.gettingstarted)