Well that all depends on whether you're at my market or yours!
Okay, let us pretend I don't have a this DB developers restrictions to work with, and look at this from a different angle. If the DB uses GUID's created by a SP, what would be the best method to handle duplicate GUID's in the following pseudo code:
I am assuming from comments above that the only method to check for duplicate keys without ADO spitting out an error is to query the table first for the key. Correct? So in essence the original DB's UniqueID generator is not really to relevent in this issue...
INSERT into table GUID, color, length
IF @@ERROR = 2627 THEN try again