🚀 go-pugleaf

Bill Todd [TeamB] wrote:
> FYI, a table can only have one primary key but the primary key can
> consist of more than one field. I assume the purpose of the COUNT field
> is to preserve the order in which the records were added to the table.
> If so, the COUNT field does not have to be 1,2,3. It can be any
> ascending sequence of integer numbers which means that you can use a
> generator. It is extremely difficult to number a group of records 1
> through N in a multi-user environment. If you think you must have 1,2,3
> etc. tell us why. Maybe the design can be changed to avoid that
> requirement.
>
>   

Hi Bill,
This table is a detail table hold items for each inventory (master 
table) the primary key consist of "inventory code" and "item code" for 
some reason customers need the item code to repeat for each inventory 
not to be unique all over the table also I already made all my logic 
based on those two fields , so I hope if there is a way to get unique 
value for field "item code" on multi user environment

Thanks

BTW: Is there a problem in the news group server many times I get post 
message refused and I dont know whom I should report this to