Les Juby wrote:
I need to extract records from a database subject to conditions and
only thereafter give the users the choice of which fields to sort the
results on.
In this situation I can't write back to a temporary file and then
select all from that file on the different sort orderings.
I figured that the only way out would be to write to an array from the
first recordset set creation. Then write the report to the screen
from the array and users can choose different sort orders and it would
extract again and report from that same array.
( 1 )
Only problem is that I havn't the faintest idea of how to create and
write to the array. Or how to query it. Is it similar to the first
database report.?
Would anyone perhaps know of a simple tutorial resource that
demonstrates this method.?
( 2 )
Or do I need to think right outside the box and take the first report
in a more efficient way. Problem is that I need to take only one
record whenever the value changes in a particular field. Could my SQL
statement use ordering on one field to take the recordset but order on
another field for the output. I wouldn't have tought so.
thanks
.les.
On 15 Feb 2006 13:16:28 -0800, "Paxton" <pa*******@hotmail.com> wrote:
A quick google threw up this result:
http://www.4guysfromrolla.com/webtech/072199-1.shtml
which may give you some ideas about how to accomplish the task.
Basically you can make the column heads hyperlinks passing the 'Order
By' variable in the querystring, then dynamically create your SQL query
using the variable passed in the querystring.
/P.
Thanks for that. It is pretty much what I would normally do, but I
think maybe I havn't explained the problem properly here.
My initial recordset is maybe only 10% of the database, and a whole
lot of complex ordering and filtering has happened to get the
recordset for display.
The user now needs to be able to view that recordset in different
orderings, and usually (as you've suggested) I'd be able to just
generate the search again with querystrings passed from hyperlinks in
the column titles. But I can't do that as I'd have to filter from the
database first on special orderings to get the primary recordset.
Catch 22.
The other method is to do the first filter and feed the results into a
temporary table. Then use that table for taking the different sorts
from. Problem here is that a second user could put results in there
while the first user is still looking at his different sorts. And
that's quite likely with this many users. To put a random ID on
records with a session variable to keep to your results only is the
worst case solution. This table could then get huge, would need
maintenance, and could corrupt. How do you clear it out without
wiping out someone else's results-in-progress.?
That's why I thought an array would be the solution. It's private (in
memory) for each user, fast, and disappears when they do.? Wouldn't
that work.? But can you use it like a normal table.?
.les.