The other thought is that I could put this info in a table that gets updated nightly. If the user want to refresh the report then that is their choice.
What about this? Jose on 7/11/2002 11:19 AM, Len Wright at [EMAIL PROTECTED] wrote: > I have written several reports that sound similar in scope to what you > are doing. My strategy is to provide the user with several selection > fields to build the query based in the user's input, and then bring back > a resultset that matches the selection fields. > > if your categories and subcategories fields are indexed, then this > approach is very quick and you don't bring back a bunch data that > doesn't get used. > > > > Regards, > > Len Wright > Plus International Corp > www.plusinternational.com > > Direct: 604-415-2384 > Fax:604-415-0830 > > >>>> [EMAIL PROTECTED] 07/11/02 08:20AM >>> > Before, I waste a lot of time going down the wrong path I would like to > know > the most efficient way to handle generating reports from a huge array. > > Here is the deal. I need to generate a cost report of repair orders > that has > 7 categories and three sub categories. Is it better for me to do one > search > and generate a huge array to manipulate through filters, do a bunch of > little searches or put the Results array into a JavaScript array and > let > JavaScript handle the gory details? > > Thanks in advanced, > > Jose -- Webologies 150 Robinette Drive Waynesville, NC 28786 828.627.1994 http://www.webologies.com ---------------------------------------------------------------------------- "You can't make an omelet without breaking eggs" Boris Badenov ---------------------------------------------------------------------------- ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
