Navigation bar and linked pages????

[robert swanson]

I have a grid_link page with parent spouse and children grids on it. The navigation bar has Edit and Add buttons. I want to ensure that when either of these is selected the next page is filtered to the same record instead of the first record which is what I get now.

I thought of using a session.link variable but I can't find where to define it on the grid link page. I thought that something like

addspouse.a5w?descendEditBox_link_1c=Key={session_link}

would work as a URL.

A second problem is how to define a back button on the navigation system.

Any help would be appreciated.

[Edward Larrabee]

The syntax for URLs with filter expressions is different when using a Navigation System component. Take a look at Calling a Filtered Grid Component from a Menu.htm

[robert swanson]

Thanks Edward but thats not quite what I want.

I want a dynamic URL for the menu. The grid I'm coming from is read only and for a specific record. I want the client to click on add or edit and go to a new page where this is allowed for the same record. The security level for the add and edit menu selections is higher than the casual visitor is allowed.

My main problem is not defining the link for the nav bar but determining the link or filter for the current page. I've just started to play with the following which didn't work

with tmpl_GridLinker
style_name = "WinXP"
edit.TargetPage = "page2.a5w"
componentName = "descend"
if eval_valid("dbf.link") then
session.link = dbf.link
else if eval_valid("dbf.filter") then
session.filter = dbf.filter
end if
end with

Can you also tell me the syntax to place in the url for a BACK button on the nave bar.

[robert swanson]

I got a session varaible to be set to the link data using

session.link=substr(request.query_string,at("=",request.query_string))

but now how do I add this to the url in the nav bar or is there a way to set a filter up to control subsequent pages.

[robert swanson]

Found better way

do a search for Creating a Session Variable when Clicking on a Link .

Apply the session variable to the overide section of the grid linker like

dbf.filter=field = session.variable

[Lenny Forziati]

Robert, thanks for updating us with your solution. Hopefully it will help others in the future.

-Lenny

do a search for Creating a Session Variable when Clicking on a Link .

Apply the session variable to the overide section of the grid linker like

dbf.filter=field = session.variable

[peteconway]

example1.9: Linking from on page th another - showing selected records

This was one of the first things I wanted to do, the anser I found was in example1.9: Linking from on page th another - showing selected records.

It's very difficult to understand the explanation given, but to cut it short it's the job of the "alias" name to get the record using _filter, if you alias is entrytoedit, then the filter would be entrytoedit_filter. You build this with the Link Address Builder that launches when you click Link Address under the Link Properties tab of the Gridbuilder/fields.

This worked for me.

parentedit.a5w?entrytoedit_filter=Parent_id={Parent_Id2} see 1.9 and it will become clear.

[robert swanson]

Peter I had no problem with that. What I wanted was to have subsequent pages with the same filter but navigating to them would be done by using the navigation system.

I should explain that each page shows a columar grid for a descendent, and for a spouse, and a tabular grid for any children.

When you look at the record, which does not allow editing, clients with the correct security level will see buttons on the navigation bar to edit either the descendent or spouse data or add a spouse or child.

I wanted to ensure that only that record would be modified

Modifying your filter to

parentedit.a5w?entrytoedit_filter=Parent_id={Parent_Id2}& session.variable={parent_id2}

This sets up a session variable to parent_id2 then you go to the grid link components you've set up for adding and editing and over-ride the setting by adding
DBF.filter = "parent_idkey = " +quote(session.variable)
to the overide section.

Hope this all made sense