Yes, order number is created from the identity field and corresponds to the record number for the Orders table.
First indication the order is invalid is when we attempt to authorize the credit card used for the order and find it's denied because billing information on the order does not match that for the credit card. When we research the particular order further we find the person's name on the order matches a previous order in the system. The previous order has different CC number and order items. Can you elaborate more on your statement about insert failure and whole lot rolled back? It's our understanding the way things should work when two orders are submitted at the exact same instant is that both transactions to insert the info into the database tables should succeed at some point in time. As I mentioned in original explanation of the problem we are finding a "hole" in the Orders table and finding that 100% of the time we find these holes the order # immediately preceeding it is a problem order. From your statement about transaction rollback are you implying that a hole in the table records is not by itself a problem? -------Original Message------- From: [EMAIL PROTECTED] Date: Thursday, February 13, 2003 11:25:18 AM To: CF-Talk Subject: RE: Corrupt records inserted into SQL database I assume that the order number is being created by an identity field? I think that if you create a record with one of your insert statements and then another insert fails and the whole lot is rolled back that number that was assigned is lost - but this is fine as the number is inconsequential really. Can you elaborate what you mean when you say "invalid orders". -----Original Message----- From: Ben Densmore [mailto:[EMAIL PROTECTED]] Sent: 13 February 2003 16:14 To: CF-Talk Subject: Corrupt records inserted into SQL database Hi everyone, We are having a problem with a custom order entry system application we have written in ColdFusion using MS SQL 7 database. The problem appears to be that intermittently invalid orders are getting into the system. Frequency is approximately 2 invalid orders every day out of about 120 orders. In addition, we've noticed that 100% of the time for each invalid order there's a hole in the Orders table of the database where there's at least one record immediately after the problem Order table record which does not exist. For example, if Order record # 3500 is found to be invalid, record # 3501 does not exist in the table, but there is record # 3502, 3503, etc. We are using a Begin Transaction, Commit Transaction statement surrounding the multiple SQL INSERTS to insert records into the SQL database. Anyone have any ideas on what might be wrong? Thanks, Ben Ben Densmore Web Developer TouchStone Software Corp./eSupport.com, Inc. 1538 Turnpike St. North Andover, Ma 01845 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
