Linking problem between pages??? Help

[robert swanson]

I have a grid with a linking field called key. I want the user to go to a new page for the detail view which is a gridlink component.
The parent grid is call Decend_disp_Box and the dbf is Decendents.dbf
The linked component is called Linked_disp_box
The page is called view.a5w and contains a reference to x_GridLinker.decend_disp_Box.

I have tried every combination of the following link code on the calling grid
view.a5w?x_GridLinker.Decend_disp_Box_filter=key="{Key}"
using all of the above names and noting works. I alway get the correct page but with the first record

Any ideas would be deeply appreciated :D :D

[Peter.Wayne]

I have a grid with a linking field called key. I want the user to go to a new page for the detail view which is a gridlink component.
The parent grid is call Decend_disp_Box and the dbf is Decendents.dbf
The linked component is called Linked_disp_box
The page is called view.a5w and contains a reference to x_GridLinker.decend_disp_Box.

I have tried every combination of the following link code on the calling grid
view.a5w?x_GridLinker.Decend_disp_Box_filter=key="{Key}"
using all of the above names and noting works. I alway get the correct page but with the first record

Any ideas would be deeply appreciated :D :D

I'm not sure what you're trying to do, but your filter, translated into plain English, says:
show the view.a5w page, and put a filter on the parent table (grid) in which the "key" field is what is found in {key} -- which I would think would just redisplay the same page you are on when you call the link.

[robert swanson]

Better explanation

Sorry I wasn't clear. The details in the previous post were all for the target page and I'm coming from another page.

let's start from scratch. I have 3 databases, parent(descendents), spouse, and children. the first page has two linked grids showing both parent and spouse and is keyed with a tree type structure. Selecting the key would take you to another page containing a detailed parent grid, spouse grid, and children grid.

Selecting a key on the child grid would reopen the page with the child as the parent together with their spouse and children.

I guess you could call this drilling down. The thing that I'm confused about is the syntax to be attached to the calling field. I,m not sure whether to use the grid componet, the link grid componet or the reference to the gridlinker on the destination page( which is what was illustrated. ) The link genie is of little help.

Also is it possible to use the same database for both the parent and multiple children in two different grids at the same time. (maybe by using different alias???)

[Selwyn Rabins]

Have you looked at example 1.9 in the sample web app that ships with a5. This seems like it does what you want.

[robert swanson]

Thanks Selwyn I did try what was in the sample
here is the link field { view.a5w?descend_filter=key="{Key}" }
and here was what was missing from my destination page

with tmpl_GridLinker
style_name = "WinXP"
edit.TargetPage = "page2.a5w" What does this do
componentName = "descend"
end with

It appears that this works with a grid component but I'm using V7 and a gridlink component with a parent and two child components and I don't know how to reference parent. The above example references the gridlink and it doesn't work. I get the new page but only the first record not the one I wanted.

[Peter.Wayne]

Selecting a key on the child grid would reopen the page with the child as the parent together with their spouse and children.

Unless I'm mistaken in what you're doing -- when you select a linking field on the child, if you want to drill down to the child, you should open a different page based on either (1) the child table alone, or (2) an inverted set with the child as parent. If you keep going to the same page then all you'll get is the same page all over again.

[Selwyn Rabins]

the statement: edit.TargetPage = "page2.a5w"

inside the component you can define a target page that will be opened after the user clicks the 'submit' button.

all that we are doing here is overriding the setting that was defined inside the component to be something else.

the ability to override settings in a component at runtime is very powerful because it makes components highly reuseable.

[robert swanson]

Everyone seems to be missing the main point.

What do I put in the linking field on the source page to get to the destination page which contains a gridlinker component? All the instructions I can find take me to pages with a single grid not a gridlinker which is new in V7.

[Selwyn Rabins]

filtering records on a page that has a GridLinker

Creating a URL to open a page that contains a GridLinker, and filtering the page so that only selected records in the parent Grid of the Gridlinker are shown is no different than creating a URL to show a page with a Grid.

For example, take example 3.1 in the demo app that ships with Alpha Five.

This page shows a gridLinker with two grids. The parent grid is based on the Invoice_Header table.

Say you wanted to open this page and show just invoice number "00005"

Here is the URL:

http://localhost:8070/Web_Applications_Demo/default/Orders_wItems.a5w?OrderHeader_filter=invoice_number="000005"

(in this case I am running the server on my machine using port 8070. in your case, your machine name and port might be different).

In the above example, the page that we are opening is 'orders_witems.a5w'.

This page contains a gridlinker.

The alias of the parent grid in the GridLinker is 'orderHeader' (the alias name is defined when you create the GridLinker)

The query Parameter OrderHeader_Filter is used to specify the filter expression that is applied to the primary grid in the GridLinker.

[robert swanson]

Thanks Selwyn. I didn't want to hyperlink because I only coming from pages within the DB. However this worked

View.a5w?decend_disp_box_link_1c=key={Key}

Thanks