>>Shouldn't you also replace the TableName here?
>>
>>> REPLACE NextId WITH 1
>>> liKey = 0
>>> ENDIF
>>> UNLOCK
>
>It probably never went into that condition. In my case, I don't have that condition. As developers we always add those records in the unique id table at development time. :) But, yes, it might be a good idea to put it there just in case we forget it during development.

I know. :) This type of code can be very useful when you have an app in production and the new version has one or more new tables. This way, you don't need to worry about the table of ids. I have this code for config table also. And I discovered that is extremly useful as is very probable the client will ask for some more config options when the app is already in production.

VLad