In Microsoft Office FrontPage 2003, if you filter a Data
View from multiple filtered Data Views, you may experience unexpected results.
When you view the final filtered results, the data is incorrectly filtered. The
following diagram provides a sample scenario, where Data View 4 is a filtered
Data View that is derived from previously filtered Data Views:
Data View 1
Data View 2 Data View 3
Data View 4
In this example, when you configure a Web Part connection from
Data View 2 to filter Data View 4, and then you configure a Web Part connection
from Data View 3 to additionally filter Data View 4, the filtering information
from Data View 2 may be lost.
Note A Data View is also known as a Data View Web Part.
This behavior may occur if both of the following conditions
You filter a Data View from multiple filtered Data
FrontPage 2003 filters the Data Views through the Web Part
connections by using the Filter View Using Data Values From
When both of these conditions are true, when you click a
hyperlink in one of the middle-tier Data Views in the filtering chain, the data
that is sent from that Data View may inadvertently clear the filter information
that is sent from other middle-tier Data Views. This causes the other
middle-tier Data Views to send the data in the first row instead of the data
that you last specified. Therefore, the final filtered results are not what you
To work around this behavior, you can filter data by using
the Modify View Using Parameters From action in the
Choose the target Web Part and action for the connection
section of the Web Part Connections Wizard when you create a Web Part
connection. This action permits the Web Parts to set the value of an Extensible
Style sheet Language (XSL) parameter through a Web Part connection. You can use
the XSL parameter to filter data. This achieves the same effect as the
Filter View Using Data Values From action.
data by using the Modify View Using Parameters From action,
follow these steps:
Click inside a row of the final Data View.
On the Table menu, point to
Select, and then click Row.
On the Data menu, click
In the right pane, click Create, and then
click Show content.
Specify the filter criteria.
To do so, in the
Field Name column, click a field name, in the
Comparison column, click Equals, in the
Value column, click [Input Parameter], and
then click OK.
Right-click the middle-tier Data View that you are using to
provide the data, and then click Web Part
If you have an existing Web Part connection, click the Web
Part connection, and then click Modify.
click Add to add a new Web Part connection if the Web Part
Connections Wizard does not start automatically.
In the Web Part Connections Wizard, click Provide
Data Values To in the Choose the action on the source Web Part
to use for this connection list, and then click
Under Choose the page containing the Web Part for
the connection, click the appropriate option, and then click
Under Choose the target Web Part and action for the
connection, click the target Web Part in the Target Web
In the Target action list, click
Modify View Using Parameters From, and then click
In the Columns in
WebPartName column, click the cell that is
next to Input Parameter, click a column value to map the field
value from the source Web Part that contains the correct data to the input
parameter, and then click Next.
Click the column that you want in the Create a
hyperlink on list, and then click Next.
This procedure causes the input parameter to affect the
rendering of the XSL Transformations (XSLT) code. The view will appear filtered
when the middle-tier Web Part connection is triggered.
For more information about FrontPage 2003 Web Part
connections, click Microsoft Office FrontPage Help on the
Help menu, type Web part connections in
the Search for box, and then press ENTER to view the list of
topics that are returned.