Yes, Jim, that looks like the way to do it all right, and I guess that doing so *would* ensure that there was no effect on the visuals.

But I can tell you that repeating a ItemID *does* have an effect on the visuals - the item goes where the old one was and there is nothing that I could do about it.

This was a long while ago, and I tore my hair out for over a day before I found the KB article saying that 'keeping the ItemID on RemoveXxxx was "by design" '. Thing was, I didn't even need ItemID but seemed forced into it by AddListItem.

Discovering the List property, I have successfully evaded AddXxxx ever since.

Cheers,

Jim N



SNIP
>Jim,
>
>Thinks of ItemIDs like surrogate PKs, don't ever reuse them, just add the new item with a new itemid using the NewItemID property and adding 1 to it.
>
>ListIndex has an effect on the visual appearance of the list but ItemID has no effect on the visuals. ItemID is strictly an internal ID assigned to each item in the list that stays with that item through its life (a sort of PK).