>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