So you have a page, "Page1" which captures some criteria, and then performs
a database query, and passes those results to "Page2" for display.
If it's a particularly small amount of XML, I suppose you could use the
query string, though you want to encode your querystring;
Response.Redire ct("page.aspx? " & Server.UrlEncod e (ds.WriteXML))
But that seems like a particularly risky way to use a querystring.
It makes more sense to me collect your criteria in Page1, then pass the
actual query parameters to Page2, and have Page2 do the query itself. In
most cases the query params will take much less space to transmit than the
query results. Also it makes Page2 more generally usable [barring special
security concerns].
Another option is to do the query, cache either the query or the result in
the database, and then pass the queryID to Page2. That's a useful approach
for very large complex queries, especially if you want to keep a history of
queries a user has run. I use that for real-estate sites, where the user
can have hundreds of criteria, and the broker needs to know what the
customer is searching for.
/// M
"Steven J. Reed" <St*********@di scussions.micro soft.com> wrote in message
news:61******** *************** ***********@mic rosoft.com...
I must be missing something, because this should be easy to do.
After the user has selected several options on a page, I do a database
query which returns a few records that I want to pass to another page via XML.
How do I do this?
I typically Response.Redire ct around my app, including various
parameters. Do I just include the XML as a parameter as in:
Response.Redire ct("page.aspx? " & ds.WriteXML)
That just doesn't seem right.
If you would be so kind as to include both what the sending and receiving
should be doing in any example it would be greatly appreciated!