Angelo,
You might want to post the entire CURSOR procedure. If you are using a cursor, shouldn't you using: .WHERE CURRENT OF cursor. Also, can you just use one command to do the entire update without a cursor? Javier, Javier Valencia, PE O: 913-829-0888 H: 913-397-9605 C: 913-915-3137 From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Saturday, April 26, 2014 4:03 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Declare cursor timing. Dennis The update statement is Update ctrectyd set canceled = .startdat where receipt eq .vrecnumb Thanks Angelo _____ From: [email protected] To: [email protected] Date: Fri, 25 Apr 2014 10:49:53 -0500 Subject: [RBASE-L] - RE: Declare cursor timing. Angelo Show us the update command. Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, April 25, 2014 9:34 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Declare cursor timing. I have an issue on timing. I have two tables, one holds daily transactions and the second holds customer orders. The daily transaction table could hold from 10 to 500 records. The customer order table holds approx. 40,000 records. I am just reading a daily transaction, looking it up by order number and updating the processed date I the customer Order table. In testing I found the following results: If I key an update it is complete in just a second. If the daiily table has 5 records it takes approx. 4 1/2 seconds per record to process. 5 records take 4.5 seconds per record, 10 records take 8 seconds per record, 20 records take 15 seconds per record, 30 records take 24 seconds per record. Why the increment in processing time, any suggestions? If I key an update
