I can't use an autoinc field because the table in question stores counters for a variety of different processes in the application. I need a way to ensure that each process can get a counter from this table and update it by 1 so that the next process will get the next number.

Any ideas?

>>I want only to understand (for me), if this is good solution to use field with type Integer(AutoInc).
>
>I work mostly with MS SQL Server where we're using Identity columns (which is similar to VFP AutoInc) in most cases. However, I would rather use ANSI SQL Sequence which gives more flexibility but is not implemented by SQL Server 2000.