Thank you Raymond. I figured it was working with the decimal as a string but I was not sure and I did not know it was limited to just strings. I like your idea of categorizing my price ranges so I can set my criteria against a string.
Raymond Camden wrote: > Verity does string based searching, not numerical base searching. What > you may consider is an alternative. All products that are < 20 bucks > are considered cheap. When inserting the data, use a criteria, or a > category, of cheap. > > > On 6/20/07, Matthew Lesko <[EMAIL PROTECTED]> wrote: > >> Well I have a problem with a verity search I am doing. The collection is >> based off a query of product data. My collection has cf_custom2 data in it >> which represents the products price. When I search the collection with: >> >> criteria="CF_CUSTOM2 <= 19.99" >> >> I will get results with CF_Custom2 with values all over the place, like >> 108.95. The interesting thing is I will not get any price that do not start >> with a 1. I have tested with other numbers in the criteria and they all >> behave the same. >> >> Am I missing something on how verity execute this search. It seems to work >> great when I use the = operator but returns unwanted results when I use the >> other numeric operators. >> >> To give this some purpose, what I am trying to do is a price range search of >> my collection. >> >> Any help would be great! >> >> >> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 and Flex 2 Build sales & marketing dashboard RIAâs for your business. Upgrade now http://www.adobe.com/products/coldfusion/flex2?sdid=RVJT Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:281611 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
