You will need to wrap cftransaction around the code, this will allow multiple queries to occur. What this means is that for instance the database access is paused until it is free, a FIFO scenario.... Have a commond variable for example, application.next_license Basically the idea behind this would be to set it if not defined, then when you do a query for the next available number you can then compare it with the last known use. Combining these two tricks might solve the problem at hand. -----Original Message----- From: Stewart, Mark [mailto:[EMAIL PROTECTED]] Sent: Friday, 19 May 2000 11:56 PM To: '[EMAIL PROTECTED]' Subject: RE: Help! Try adding a check in your system that checks to see if the lisence number you're trying to assign is already assigned to someone else. If it's already assigned, generate a new number and go through your check again. Mark -----Original Message----- From: aslam bajaria [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 18, 2000 3:09 PM To: [EMAIL PROTECTED] Subject: Help! Hi All, I have a problem. The way the system works right now at my company is that the operator opens up a customer's account using the customer id and gives the customer a license number. The license number is generated automatically. Each time a license number is assigned, the file having the license number gets incremented automatically. For example operator A approved cust_id 111 and assigned him license number 90000011. If operator A opens up another customer account, say customer number 212, the available license number will be 90000012. The problem I am facing is that if operator A and operator B open up two different customers (say cust_id 250 and cust_id 366), then it shows to both of them that the available license number is 90000012. The available license number gets incremented ONLY when the operator approves the customer's request for license form. Is there a that if operator A see's 90000012, then operator B should see 90000013. But again, the question is if operator A cancels the application, then the available number for operator B should be 90000012 and not 90000013. Is it possible that if operator A cancels the application, then the operator B's screen should automatically change and the available number should be 90000012. Does someone have an idea on how to solve this? Has any of you encountered this problem before? Thanks. M Baig __________________________________________________ Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/ ---------------------------------------------------------------------------- -- Archives: http://www.eGroups.com/list/cf-talk To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. ---------------------------------------------------------------------------- -- Archives: http://www.eGroups.com/list/cf-talk To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. ------------------------------------------------------------------------------ Archives: http://www.eGroups.com/list/cf-talk To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
