following from Spike's post and the link http://affy.blogspot.com/2003_03_02_affy_archive.html#90405845
is this: <quote> Updating Information: If not properly handled, duplicate records can be created in the database. Duplicate inserts can be eliminated creating a UUID value beforehand and making it part of the form information. </quote> now that's refering to the logic (CF, ASP, PHP, whatever) creating the UUID, yes? if not and this is refering to the DB creating the UUID's then that's no diff than inserting a new (blank) record, getting the @@IDENTITY and then doing an update with the real data. so taking Spike's point a bit further, what could go wrong if there are multiple logic tiers (not just CF) all creating their own UUID's for inserts? this would be madness , surely, and you'd leave it up to the db to generate the UUID's? --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
