>Thank you very mach for your answer. I've tried to do the same thing with new records, but have discovered the following problem: if I obtain value from common routine for the primary key in new record in multi-user environment, such value may be invalid by the time of tableupdate(). Other then that, it looks nice. Thanks again.

Sorry, I'm confused. Why would the key become invalid? If you get a new key Id from a table (view) and update the keys table/view at that point so that the next user gets the _next_ key, I cannot understand why they key you obtained would become invalid.

This implies that consecutive keys is an absolute requirement, and even if that is the case, you can wait until the user chooses 'save' before obtaining the keys. If you obtain the key id from the keys table/view at the end of the input, and right before the table update, it really shouldn't be a problem.

Alan