Hi Dragan

Yeah, I'm always chary of the dangers when using Alter Table. Of course I would have to ensure exclusive use of the table anyway. In case another user wished to create an ALLZONES record, at the same time, via its own form, where the NewID() function would come in to play, to get the next Zone ID.

The main thing that's troubling me now, about this whole shibang, is that the Zone IDs I'm importing are welll beyond the range of the existing Zone records. e.g. the current highest incremental allocated Zone ID could be, say, 1100, whereas the import could introduce a zone ID of, say 9013 (as this does). Later, when and if NewID() reaches 9013, and happily allocates it, I'll get the uniqueness violation!

Hmmm, I think I'll have to do some supplemental coding in NewID() to avoid this.

Cheers

Terry

>>
>>I've just experimented and done it 1st time with Alter Table!
>
>Alter Table is a way, though it's not without its dangers - I think that's the reason you need exclusive access to the table to do that. You're basically changing table's structure, even though this time it's not something in the table's header or structure, but rather in the related record in the dbc.