Jon, >> Can anyone tell me if there's a limit to how long IE >> will wait for a page to load? >Yes, there is, but I'm not sure exactly what or how it's triggered. On my >box IE seems to give up after about a minute (at least, that's what's >happened when, say, DNS servers haven't been available)
Hmm, I'm starting to think I'm doing something very wrong. The more simple reports are taking between 5-20 minutes, and I've had a report compile successfully after about 50 minutes. :-o >> Alternatively if anyone can suggest a different approach >> to compiling the report. >We have many heavyweight reports on our intranet that take a couple of >minutes to run, and our PHBs seem quite happy with a system whereby the >results or a link to a temporary page containing the results are emailed to >them (I prefer generating a temp page, personally - you can schedule it to >regenerate every hour or day or whatever) >Many high-volume sites (slashdot, for example) use this technique, as a >webserver can spit out a static HTML file a lot quicker than it can run a >script which queries a database. Unfortunately, the reports are based specifically on user input, various inputs including date ranges. >reports (disclaimer: I know next to nothing about CF) Me neither :-) but may be worth looking into. >> I'm now pulling one recordset, and while looping through >> that pulling a second set of data based on the first recordset. >Generally speaking, this is not a good idea, and quite often the desired >effect can be achieved by judicious use of joins - if you explain what >you're trying to achieve, someone may be able to suggest a better way to >structure your data/code so that you can avoid or minimise this. OK, this may be quite messy though. We have tables relating to the query: Individuals IDCards Tickets (Link table for 3 above tables) Locations (Linked 3 times from Ticket table (Purchased from, Travels From, Destination)) Refunds (Link table for tickets and refunds) Discounts (Linked from Tickets table) I think thats all for this report. Anyway, I was pulling the data on live tickets linking the tables allowing the user to specify whether the tickets were purchased/departing from a specific location, a user defined group of locations, or all locations, the data range to search on and the type(s) of tickets to search on. This was working OK, except not the client wants to only pull one of any individaul in the given report regardless of how many tickets they may have that meet the report criteria or refunds, only showing the first valid ticket relating to that customer, but showing a count of how many tickets were found to be valid. I'm now running the same original query, except only pulling the individual's details and a count of each individual, grouping by individual details. Then running through that recordset, pulling the top 1 of the relevant ticket/journey/refund/idcard information ordered by date and writing the data to the page. An average query would be pulling at least 10,000 individuals. I hope I've explained that well enough and not confused the situation. Cheers, Adam. ____ • The WDVL Discussion List from WDVL.COM • ____ To Join wdvltalk, Send An Email To: mailto:[EMAIL PROTECTED] Send Your Posts To: [EMAIL PROTECTED] To change subscription settings to the wdvltalk digest version: http://wdvl.internet.com/WDVL/Forum/#sub ________________ http://www.wdvl.com _______________________ You are currently subscribed to wdvltalk as: archive@jab.org To unsubscribe send a blank email to [EMAIL PROTECTED]
