Robert Sorrells
|
| Posted: 07/19/2003, 6:14 AM |
|
I've got a search/grid procedure that was generated by the wizard. The
user will enter their search criteria and see the filtered list, as normal.
I have a 2nd very simple grid table called Export. What I would like to do
is to take the current filter criteria of the main search/grid procedure,
and somehow transfer it to the new table when the "Export" link is pressed.
One way I thought of might be to somehow grab the SQL statement of the main
search/grid procedure and save it to a session variable, and use it for the
export procedure.
I tried grabbing the "mydata.DataSource.Where" and putting it into a
session variable, but it did not contain the entries from the search form.
Thanks,
bob
|
|
|
 |
Robert Rodgers
|
| Posted: 07/19/2003, 7:10 AM |
|
create your link for the export and ccs should concatenate the search params
onto it if you have the preserve parameters set to get or both
rob
--
"Every absurdity has a champion to defend it"
Oliver Goldsmith
++++++++++++++++++++++++++++++
"Robert Sorrells" <rsorrellsU@KNOWmindspring.com> wrote in message
news:bfbg8f$mrr$1@news.codecharge.com...
I've got a search/grid procedure that was generated by the wizard. The
user will enter their search criteria and see the filtered list, as normal.
I have a 2nd very simple grid table called Export. What I would like to do
is to take the current filter criteria of the main search/grid procedure,
and somehow transfer it to the new table when the "Export" link is pressed.
One way I thought of might be to somehow grab the SQL statement of the main
search/grid procedure and save it to a session variable, and use it for the
export procedure.
I tried grabbing the "mydata.DataSource.Where" and putting it into a
session variable, but it did not contain the entries from the search form.
Thanks,
bob
|
|
|
|
Robert Sorrells
|
| Posted: 07/19/2003, 7:55 AM |
|
It works great.
Thanks!
Bob
"Robert Rodgers" <rrodgers@sylvancomputing.com> wrote in message
news:bfbjge$r1j$1@news.codecharge.com...
create your link for the export and ccs should concatenate the search params
onto it if you have the preserve parameters set to get or both
rob
--
"Every absurdity has a champion to defend it"
Oliver Goldsmith
++++++++++++++++++++++++++++++
"Robert Sorrells" <rsorrellsU@KNOWmindspring.com> wrote in message
news:bfbg8f$mrr$1@news.codecharge.com...
I've got a search/grid procedure that was generated by the wizard. The
user will enter their search criteria and see the filtered list, as normal.
I have a 2nd very simple grid table called Export. What I would like to do
is to take the current filter criteria of the main search/grid procedure,
and somehow transfer it to the new table when the "Export" link is pressed.
One way I thought of might be to somehow grab the SQL statement of the main
search/grid procedure and save it to a session variable, and use it for the
export procedure.
I tried grabbing the "mydata.DataSource.Where" and putting it into a
session variable, but it did not contain the entries from the search form.
Thanks,
bob
|
|
|
|
Robert Sorrells
|
| Posted: 07/19/2003, 8:36 AM |
|
I noticed that the names & values of unchecked controls are not passed as a
parameter, whereas checked controls are. I had to convert my checkboxes in
my search to drop-boxes.
Is that a bug?
"Robert Rodgers" <rrodgers@sylvancomputing.com> wrote in message
news:bfbjge$r1j$1@news.codecharge.com...
create your link for the export and ccs should concatenate the search params
onto it if you have the preserve parameters set to get or both
rob
--
"Every absurdity has a champion to defend it"
Oliver Goldsmith
++++++++++++++++++++++++++++++
"Robert Sorrells" <rsorrellsU@KNOWmindspring.com> wrote in message
news:bfbg8f$mrr$1@news.codecharge.com...
I've got a search/grid procedure that was generated by the wizard. The
user will enter their search criteria and see the filtered list, as normal.
I have a 2nd very simple grid table called Export. What I would like to do
is to take the current filter criteria of the main search/grid procedure,
and somehow transfer it to the new table when the "Export" link is pressed.
One way I thought of might be to somehow grab the SQL statement of the main
search/grid procedure and save it to a session variable, and use it for the
export procedure.
I tried grabbing the "mydata.DataSource.Where" and putting it into a
session variable, but it did not contain the entries from the search form.
Thanks,
bob
|
|
|
|
|
