Hi

I should have added on the original post that the control needs to remain in SQL as other platforms will be calling the same stored procedures, i.e. ASP, VB etc. Sometimes the best solution isn't necessarily what a text book tells you, hence I wanted people who'd 'had a go' to let me know what they'd done to complete record locking.

In reality, the record that's being locked is a lookup record that tells SQL what the next unique ID for a selected table is, so, the locking itself would be very quick, and the number of fields to be updated would be minimal.

Regards