>>IMHO, I would not use Identity Column for something that user will see and account for. I would have a PK - Identity Column - in every table as a way to have the view or a Cursor Adapter cursor to update the table.
>>Then create a field for the code to indicate whatever it must indicate (e.g. the rage). That is, the user then will not see the PK but rather a business field value. What I am trying to say is that PK field/Identity should be a separate field from the business field you use for your suppliers.
>>Hopefully it makes sense.
>
>I'll take into account your advice. I guess, it makes it easier to develop the auditing routine.
>
>Thanks
Yes. In my auditing routine, the audit table stores the PK of the table being audited. Therefore, I can easily see which record was edited or deleted or added. And based on this, I build an audit report showing in chronological order which records were altered.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
