Interesting... I think I all-too-often assume someone's using the dame DB design paramters as I do, and I completely missed this until you said something, Jochem.
I always, always, always set the first column in my table to primary key, identity, and often (but NOT always) a clustered index. I read right past the "I have a duplicate" part... and making the column an ID or using a UNIQUE constraint would have prevented the second record from occurring at all. Good catch. J On Tue, 08 Mar 2005 14:52:09 +0100, Jochem van Dieten <[EMAIL PROTECTED]> wrote: > Tony Weeg wrote: > > > > i have two records with the same acctNo, and there should only > > be one! > > Define the field as UNIQUE. > > > <cftransaction> > > Make this transaction serializable. > > Jochem > -- Continuum Media Group LLC Burnsville, MN 55337 http://www.web-relevant.com http://cfobjective.neo.servequake.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:197820 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=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
