Ok, I actually have another one in source control that works. The one
you have is generated directly from the ide without any changes from me.
Jeff
David Churvis wrote:
Hi Jeff,
Take a look at how CompanyViewForm.cfm is structured. Instead of putting
the Office List inside the Company View Form, you put the Office List at the
same level. In effect, this just creates a view form and a list on the same
page, rather than a list nested within a view form.
HTH,
Dave
----- Original Message -----
From: "Jeff Fleitz" <[EMAIL PROTECTED]>
To: "[email protected]"
<[email protected]>
Sent: Wednesday, November 17, 2004 11:18 AM
Subject: [plum] Master Detail Filtering
Build 759
Still having problems with master/detail child lists called from a
parent form. In this case, a view form. There should be a
whereClauseExtension attribute automatically built in when the template
is generated. It is not there and defaults to displaying all children
instead of filtering it for the parent primary key.
<cf_DisplayList table="Office" rowsPerPage="10" label="Company Offices"
displayALinkToThisSearchForm="No" whereClauseExtension="Office.CompanyID
= #URL.CompanyID#">
--
_______________________________
Jeff Fleitz
Tekquest, Ltd
Integrated Digital Solutions
http://www.tekquest.com
_______________________________
