If the number is actually used, update the record with more fields. If the number is not actually used, delete the record.
Thanks I guess I did not think of checking after locking the table only before.
If you need a guaranteed-unique identifier and don't have the luxury of being able to access and/or lock the main database(say in a distributed setup where records are added on offline laptops or something), you can use something called a "GUID". This is a "globally unique identifier", and if you use the algorithm used by Microsoft's Create GUID function, you're guaranteed that it'll be unique. It's much longer than 9 alphanumeric characters, however... -- Derek _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
