I do something similar to what Lorne does, although I use a UUID so that there is NO chance of collision (if you use time like that you aren't truly safe). There is no need to mess around with cflocks, cftransactions etc. with this method, and it works unmodified on all db platforms (SELECT @@IDENTITY is only good for SQL Server and maybe Access... other platforms require different platform-specific methods to do the job).
I like the UUID so I can write one solution and apply it to all platforms (something not everyone needs to do, admittedly) and I usually find a use for a UUID one way or another within a db record, so its not really an 'extra' field in my table.. -- --mattRobertson-- Janitor, MSB Web Systems mysecretbase.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:206289 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
