>The current system I'm working on, using a table with one record on the SQL Server. We have unique Id's across the whole system (therefore no Customers with the same ids as Employees etc..)
>
>We have a stored procedure which returns back the next id. It perofrms the locking and manages conflicts.
>
>You could have one row for each table in your system of course.
>
>Something you might try is having two connections to your database - one for accessing the data ( we use SQLEXEC not views, but you can share all the views on one connection), and one for accessing the next id. That way, if you have any transactions, then the id table won't be locked or rolled back if something goes wrong!
>
>Hope this helps.
>
>Ian
>
Hi Ian,

Thanks very much. I'll have to look into this as I don't know enough about it yet.