>>To be honest, it was my error in this stored procedure, which I just fixed. However, what if NextID table could not be opened or locked? In this case this function still would return 0 and we would end with 0 as Primary Key...
>
>I think my equivalent function returns -1 instead.
>
>In any case, you could have a trigger rule that forbids 0 (or -1) as PK.
>
>Hilmar.

Hilmar,

Could you please expand this idea? I've never done this before, so I'm curious, how it's done in your system? If 0 (or -1) would be returned, this record should not be appended at all. How can I achieve it?

Thanks a lot in advance.