I have a ItemID column within database, in which I would like to be non-editable & number progressively, in increments of one. (1,2,3,4,5...etc.)
Problem is, I already am using a Primary Key on an "ID" column. When "modifying the table", I cannot seem to find how to make
two columns both be non-editable & number progressively, in increments of one.

Changing Identity Specification to "Yes", takes the Primary off of the "ID" column.
It would be ideal to have the "ItemID" be non-editable, but even if the ItemID column was editable, I need to know how to make it
number progressively, where it will never use the same ItemID twice.

What am I missing? 



Feedback Appreciated,

-machina12

Will,

I can see how having multiple Identity Specifications within one SQL table could be conflicting/not possible.  It would be ideal to have the "ItemID" be non-editable, but even if the ItemID column was editable, I need to know how to make it number progressively, where it will never use the same ItemID twice. (1,2,3,4,5,6,7,8,9,10,11......etc.)

What am I missing? 



Feedback Appreciated,

-machina12

I guess you're right, the ID with Key could be used as ItemID in reality.
Although there are other situations where I need multiple values to stack. Similar to the ModuleID and userID methods.
Thanks for the link.