Emmitt: Do you mean, though, that they could never change
their mind and NOT add that record?
In several of our processes, like order entry for example, we use forms where the fields are all variables (but not true variable forms). The eep to add the record sets a lock on a control table, retrieves the integer value, increments it by one, stores the new value back to the control table, then releases the lock. This number is used for the order number. Always unique, never duplicated, never skipped.
And I agree with Mike and Dave. I always have an autonumber PK
on each table that means nothing to the client. But if they ALSO
want a unique number (such as an invoice number) it seems redundant
to have TWO unique numbers per table.
>I agree with Mike. I don't even let them know the autonumber PK exists.
Karen
