View Single Post
  #5 (permalink)  
Old March 3rd, 2008, 05:49 PM
RussLewis RussLewis is offline
Registered User
Join Date: Feb 2008
Location: , , .
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts

Sorry about that in the parameters but in the actual stylesheet the values for the parameters come from an ASP server-side app that merely feeds them to this stylesheet from another stylesheet masquerading as a user input form. So truthfully the parameters look like this:
  <xsl:param name="searchfield" />
  <xsl:param name="searchtext" />
  <xsl:param name="sortbyfield" />
  <xsl:param name="sortorder" />
I just filled them in (albiet incorrectly) for this post. (Sorry about that)
but your example of:
  <xsl:param name="searchfield" select="'Field2'"/>
  <xsl:param name="searchtext" select="'entry'"/>
  <xsl:param name="sortbyfield" select="'Field1'"/>
  <xsl:param name="sortorder" select="'descending'"/>
should at least make this work.
Also the part about "This entry is not readable" is one of the main things I'm trying to learn to do. While the fact that Field2 contains "entry" should qualify it for output, the fact that Field1 contains "info" should override that qualification and disqualify this record for output because no matter what the search finds in any field, if Field1 contains any standard case variation of "info" the record is NOT to be output to the table.

I'm not sure if this changes you response but I'll give your response a try and see.

Russ Lewis

Reply With Quote