TPColson
|
| Posted: 02/08/2002, 12:47 PM |
|
When using the Search/Grid form in the EmpyDir example, one can do a search,
say, by name, IE "Bob" and it returns the one record named bob. Hitting the
"back" button on the EmpDetail page, returns the user to the default
search/grid page. Is there any way to modify the parameters of the cancel
function so that it returns the user back to the search/ results of the
search for "bob" page?
|
|
|
 |
Omaha
|
| Posted: 02/08/2002, 2:02 PM |
|
I believe this issue is addressed somewhere in the event management tutorial located in the tutorials page of the codecharge support site.
|
|
|
|
Nicole
|
| Posted: 02/09/2002, 2:43 AM |
|
Hello,
you should pass search parameters to record form and back to Grid. Refer to BugTrack example default page/Bugs form and BugsRecord page/Bugs form to find how to do it.
|
|
|
|
Andrew B
|
| Posted: 02/10/2002, 11:15 PM |
|
This works for pretty much any form, and I am sure there are examples where you were referenced by the above people. This is how to do it
You want to pass 's_name' back and forth.
Your grid form should already have the search parameters in 'input' if you generated it with the wizard. Make sure the variables have [x]transfer checked, as this will add them to the link in the grid.
On your details page, you want to exactly the same thing. Say you have the first step working fine, and your url looks like this :
http://site/EmpDetails.asp?s_name=bob&id=3
In the INPUT parameters of your detail form, create a variable. Name it 's_Name' and check the transfer box. Make sure that it does not reference any db field (leave that drop down blank).
Now that form will accept s_Name as an input parameter, not actually use it for anything but keep it around anyway, and since it is marked 'transfer' it will send it along when you click cancel.
Make sure that the 'name' parameter matched exactly what you are passing. Essentially, what you are doing is copying the parameters in your search results form (the grid) into the details form, but not tying them to any DB field. This lets you transfer them back and forth without any extra custom code.
|
|
|
|
|
