New Forum | Previous | Next | (P-PDF) Developers
Topic: Execute Method vs. Recordset Object
Conf: (P-PDF) Developers, Msg: 89130
Date: 6/6/2003 12:21 AM
We have a database in which form information is saved via fdf. We are creating a control number... there is a table with two fields, a value and a name (name is irrelevant). When the form is saved, the asp page will go out to the table, check the value, increment it, and save it back. Also populating the form field with the number. It works great.
My problem lies in the speed.
I have set up two subroutines to do this. One using the Execute Method, and one using the Recordset Object. We are wanting to use the Recordset Object, because the file can be locked. According to all our books, you can't lock the record with the Execute Method.
I set up two subroutines because the Recordset Object is sloooooow. The Execute Method is fast. I switch between the subroutines to see how they both work. They both work find. Table is queried, value retreived, incremented, and saved. Value is then FDFed to the form. However, the Recordset Object way takes about 50 times longer... it can take up to five minutes after clicking the Save Form button. :(
There is another Recordset object in this asp page. However, it's in a subroutine that is hit for a different function. Also, I've changed the name of the Recordset Object so they are different, and do not see a speed change. And that other Recordset Object does not seem slow at all.
I'm wondering if anyone has insight as to why this would be so slow. Would there be some sort of conflict? I have checked the code to make sure it's not querying the DB too much... that is actually why I made the subroutine with the Execute Method, because I was testing to see if I was doing something wrong. The fact that the Execute Method works lickedy split, and the Recordset Object is slower than snot, is baffling me and my cohort. :)