Icetips Products: Icetips Xplore: Some comments from author Brian Staff 2003-03-06 -- Brian Staff Newsgroups: TopSpeed.Topic.Third_Party
This is a pure temporary solution that seems to fix the Xplore problem.
There is no guararntee it will fix any other filter problems and there's
no
gurantee it will not cause further problems.
ABQUERY.CLW
ParseBound ROUTINE
IF NOT SELF.Fields.Middle &= NULL
? ASSERT(SELF.Fields.Middle = Value)
Operator = Operator & '='
END
MakeOperator(Operator,Value,Operator,Value)
IF Value[1] = '^'
CaseLess = 1
Value = UPPER(Value[2:Len(value)]) !this line seems to fix the
filter
C55h problem in Xplore
! Value = CHOOSE (Length <= 1, '', UPPER(Value[2:Length]))
END
== end of message ======
:
Or this???
If there are any HOT fields on a browse window, Xplore assumes that they may
be
needed as locator fields when the browse is sorted by that column field.
Hence, that field then gets used by the locator class and locators are
always
cleared when scrolling take splace in the browse.
It's simple to get around the problem. In the controls that contain the HOT
fields, just modify the USE variable to be something like this:
USE(FieldX,,?YourOwnName)
Brian Staff (Phoenix)
Printed November 23, 2024, 6:10 pm This article has been viewed/printed 35263 times. Google search has resulted in 15 hits on this article since January 25, 2004. |