More efficient script

[ryushinyama]

I am trying to pull up all orders on one page so that it can be printed off in one push of a button. Once it gets to around 250-270 orders the script times out. Here is a map of what it is doing

SQL STATEMENT MAKES A SET OF ORDER NUMBERS THAT NEED TO BE LOADED

DO WHILE LOOP RUNS TILL EOF

SQL STATEMENT BRINGS IN DATA FOR PRESENT ORDER

HTML/VBSCRIPT WRITES OUT ORDER

MOVENEXT
END LOOP

PRINT BUTTON

How can I make it more efficient so I can ensure that all orders load.

That is the first question.

An answer to this question would be helpful too. What do you think would be the best way to mark them in the database. When the orders are printed the page needs to put some information into the database:

Binary that it was printed
DateTime for the date and time it was printed
And estimated weight of order

This is presently done with a form which posts the info to a second vbscript page but the orders only print one at a time.

I was thinking I could use arrays for each item and step through them in the printing function. But would I want to redim the array each loop through or would I want to run a count query on the data before making the dataset to know what size to make the array?

Lastly I need backup info when not if the printer has an issue; runs out of ink have way through and half prints 100 pages. So I would want to make a log of order numbers for each print. Do this with an array? Or append the info on to a string and break it up later?

Any ideas would be well appreciated. Thanks, Ben.

[jhardman]

Ben,

This is a very straight-forward script, I don't see an easier or more efficient way to do it. This shouldn't take super long, I have some pages that pull up close to a thousand records before timing out. Anyway, the default time limit is 90 seconds or so, you might want to set the timeout at 5 minutes:

<% Server.ScriptTimeout = 300 %>

Let me know if this helps.

Jared

[iam_clint]

make your remembering to do rs.movenext

[jhardman]

make your remembering to do rs.movenext

That's right, now that I think about it. Most of the time I get time outs, they are caused by failure to advance through a loop correctly. For example, even if your movenext is there, some errors with an appropriate error handler will break loops and make them go forever. Are you using an error handler?

Jared

[ryushinyama]

No error Handling in there as of yet. I feel that it will work just fine with the larger timeout. I will let you know when I find out. I am now having a hard time with the post. I need to mark all the orders that are printed as printed in the db. As each order pulls up the order id number gets amended to the end of a comma separated string. This I need to post to a new page. But when I post I get a http 500. I have never seen a post have a problem posting to another page unless that page just simply doesn't exist. What general causes posts to return a 500? Thanks for your help, Ben.

[jhardman]

No error Handling in there as of yet. I feel that it will work just fine with the larger timeout. I will let you know when I find out. I am now having a hard time with the post. I need to mark all the orders that are printed as printed in the db. As each order pulls up the order id number gets amended to the end of a comma separated string. This I need to post to a new page. But when I post I get a http 500. I have never seen a post have a problem posting to another page unless that page just simply doesn't exist. What general causes posts to return a 500? Thanks for your help, Ben.

When you are using a querystring it could be that a period or some other special character is messing up the URL syntax.

Jared