>>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.
>
>Good point, however I prefer to do it myself. The table that I am using for unique ids is having more than 40 fields. So, this really requires the developer to handle that. :)

Of course you prefer to it yourself. This is only like an insurance for the case you forget to do it! :)

Vlad