SInce no one has talked to you about why this is a bad idea, maybe I should. The identitiy field is the key field that other tables use to link to the information in most cases. If you cahnge it and you do not have cascading update enabled then you lose the integrity of your data. data in child tables will no longer match to the correct data. This is a bad thing and too be avoided if at all possible. If you tell us why you want to change the idneity field maybe we can point you to a less dangerous solution. Whatever you do, do not change the identity field without taking a full backup of the table first. It's better to spend the time to do this than to lose your job because your data is hopelessly and irretrievably messed up.
Questions about posting. See faq183-874