Does anyone know
about an issue regarding <@TOTALROWS> in a search results action ignoring
the "DISTINCT" rows option? Is there a known workaround that someone has
that I can implement?
This is NOT a
problem in the DBMS action, only when using the checkbox to select
"DISTINCT".
Jim Kass
Web Developer
--
Forestweb: The Source for
Industry Intelligence
Best Content -- Most Relevant -- Best Delivery
http://www.forestweb.com
(310) 553 - 0008
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
