Phil
|
| Posted: 07/04/2003, 6:22 AM |
|
I am using a page for the master record, and a page for the detail grid.
The problem with ccs's samples is they put everything on one page. I know
(I think) I have to get the master record ID to a hidden field on the page
with the detail grid. then pass that to the 3rd page which has the detail
record.
can anyone help? I have tried everything I can think of.
|
|
|
 |
DonB
|
| Posted: 07/04/2003, 8:17 AM |
|
This is easy to create.
There are just two things you need to know and do:
On every Link, there is an "Href Source" that has a place to put "Link
Parameters". On every Datasource, there is a place to put a "Where" list.
On the Link for the "master", be sure you specify the master record's
primary key (all of it, if it is made up of several columns). On the
Datasource for the detail (or any "child" record), be sure to put in a
matching set of "Where" entries.
Bear in mind the application's purpose and the security reamifications, if
any, of passing the key info via URL. If the possibility of the user
handcrafting a URL other than what you want them to have access to is a
security issue, then by all means pass the key some other way (such as a
session variable that gets set prior to leaving the master and changing the
detail Datasource type from "URL" to "Session").
The linking behavior works the same whether it's all on one page or split on
several pages: Links send Link Parameters to Datasources and Datasources
include them into their "where clause" to show the correct set of records.
DonB
"Phil" <padams@nascar.com> wrote in message
news:be3v2r$i2u$1@news.codecharge.com...
> I am using a page for the master record, and a page for the detail grid.
> The problem with ccs's samples is they put everything on one page. I know
> (I think) I have to get the master record ID to a hidden field on the page
> with the detail grid. then pass that to the 3rd page which has the detail
> record.
>
> can anyone help? I have tried everything I can think of.
>
>
|
|
|
|
Phil
|
| Posted: 07/04/2003, 11:48 AM |
|
After reading your reply, I started studying the way I was passing URL
parameters. I cleaned up all the link parameters & have a much better
understanding of this now.
I also went back and studied the ccs "master detail" sample. I duplicated
their stategy of adding a hidden field to the detail page, choosing MasterID
as the control source. I then added "BeforeBuildInsert" event to update the
hidden 'MasterID' field with the current Master ID received over the URL. I
had tried this earlier, but my link parameters were goofed up.
Thanks for pointing me in the right direction! PS: working on the 4th of
July?? As an independent consultant for 17 years, I rarely took holidays.
That's one plus about working for someone else (that and a steady paycheck!)
Nascar Daytona Beach Employees have to work today, but get next Fri off.
"DonB" <7432D63DBB01D03A196B1EDD80E8@comcast.net> wrote in message
news:be45qe$qpp$1@news.codecharge.com...
> This is easy to create.
>
> There are just two things you need to know and do:
>
> On every Link, there is an "Href Source" that has a place to put "Link
> Parameters". On every Datasource, there is a place to put a "Where" list.
>
> On the Link for the "master", be sure you specify the master record's
> primary key (all of it, if it is made up of several columns). On the
> Datasource for the detail (or any "child" record), be sure to put in a
> matching set of "Where" entries.
>
> Bear in mind the application's purpose and the security reamifications, if
> any, of passing the key info via URL. If the possibility of the user
> handcrafting a URL other than what you want them to have access to is a
> security issue, then by all means pass the key some other way (such as a
> session variable that gets set prior to leaving the master and changing
the
> detail Datasource type from "URL" to "Session").
>
> The linking behavior works the same whether it's all on one page or split
on
> several pages: Links send Link Parameters to Datasources and Datasources
> include them into their "where clause" to show the correct set of records.
>
> DonB
>
>
> "Phil" <padams@nascar.com> wrote in message
>news:be3v2r$i2u$1@news.codecharge.com...
> > I am using a page for the master record, and a page for the detail grid.
> > The problem with ccs's samples is they put everything on one page. I
know
> > (I think) I have to get the master record ID to a hidden field on the
page
> > with the detail grid. then pass that to the 3rd page which has the
detail
> > record.
> >
> > can anyone help? I have tried everything I can think of.
> >
> >
>
>
|
|
|
|
Phil
|
| Posted: 07/04/2003, 11:50 AM |
|
Forgot to mention it, but it's working now!!
"DonB" <7432D63DBB01D03A196B1EDD80E8@comcast.net> wrote in message
news:be45qe$qpp$1@news.codecharge.com...
> This is easy to create.
>
> There are just two things you need to know and do:
>
> On every Link, there is an "Href Source" that has a place to put "Link
> Parameters". On every Datasource, there is a place to put a "Where" list.
>
> On the Link for the "master", be sure you specify the master record's
> primary key (all of it, if it is made up of several columns). On the
> Datasource for the detail (or any "child" record), be sure to put in a
> matching set of "Where" entries.
>
> Bear in mind the application's purpose and the security reamifications, if
> any, of passing the key info via URL. If the possibility of the user
> handcrafting a URL other than what you want them to have access to is a
> security issue, then by all means pass the key some other way (such as a
> session variable that gets set prior to leaving the master and changing
the
> detail Datasource type from "URL" to "Session").
>
> The linking behavior works the same whether it's all on one page or split
on
> several pages: Links send Link Parameters to Datasources and Datasources
> include them into their "where clause" to show the correct set of records.
>
> DonB
>
>
> "Phil" <padams@nascar.com> wrote in message
>news:be3v2r$i2u$1@news.codecharge.com...
> > I am using a page for the master record, and a page for the detail grid.
> > The problem with ccs's samples is they put everything on one page. I
know
> > (I think) I have to get the master record ID to a hidden field on the
page
> > with the detail grid. then pass that to the 3rd page which has the
detail
> > record.
> >
> > can anyone help? I have tried everything I can think of.
> >
> >
>
>
|
|
|
|
DonB
|
| Posted: 07/04/2003, 2:05 PM |
|
Excellent news. Enjoy long weekend with one less problem to worry about.
DonB
"Phil" <padams@nascar.com> wrote in message
news:be4i9t$afh$1@news.codecharge.com...
> Forgot to mention it, but it's working now!!
>
>
> "DonB" <7432D63DBB01D03A196B1EDD80E8@comcast.net> wrote in message
>news:be45qe$qpp$1@news.codecharge.com...
> > This is easy to create.
> >
> > There are just two things you need to know and do:
> >
> > On every Link, there is an "Href Source" that has a place to put "Link
> > Parameters". On every Datasource, there is a place to put a "Where"
list.
> >
> > On the Link for the "master", be sure you specify the master record's
> > primary key (all of it, if it is made up of several columns). On the
> > Datasource for the detail (or any "child" record), be sure to put in a
> > matching set of "Where" entries.
> >
> > Bear in mind the application's purpose and the security reamifications,
if
> > any, of passing the key info via URL. If the possibility of the user
> > handcrafting a URL other than what you want them to have access to is a
> > security issue, then by all means pass the key some other way (such as
a
> > session variable that gets set prior to leaving the master and changing
> the
> > detail Datasource type from "URL" to "Session").
> >
> > The linking behavior works the same whether it's all on one page or
split
> on
> > several pages: Links send Link Parameters to Datasources and
Datasources
> > include them into their "where clause" to show the correct set of
records.
> >
> > DonB
> >
> >
> > "Phil" <padams@nascar.com> wrote in message
> >news:be3v2r$i2u$1@news.codecharge.com...
> > > I am using a page for the master record, and a page for the detail
grid.
> > > The problem with ccs's samples is they put everything on one page. I
> know
> > > (I think) I have to get the master record ID to a hidden field on the
> page
> > > with the detail grid. then pass that to the 3rd page which has the
> detail
> > > record.
> > >
> > > can anyone help? I have tried everything I can think of.
> > >
> > >
> >
> >
>
>
|
|
|
|
|
