Login
Templates, Tools and Utilities
for Clarion Developers
Templates, Tools and Utilities
|
||
|
|
|
Icetips Article
Back to article list
Search Articles
Add Comment
Printer friendly
Direct link
Icetips Products: Icetips Xplore: Using hotfields 2003-03-12 -- Brian Staff Newsgroups: comp.lang.clarion
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)
===================
For those of you that use Xplore and are running C55H you will probably know
about the filter problem, and if you look on the newsgroups you will find a
fix in ABQUERY.CLW. We have been running this fix but a customer has
reported a problem when performing a user filter using CONTAINS, it doesn't
work.
So, to fix this load ABQUERY.CLW and scroll down to the QUERYCLASS.GETLIMIT
procedure; In this procedure you will find the following snippet of code:
IF Value[1] = '^' ! When the carat is the second character i.e. *^
CaseLess = 1
Value = CHOOSE (Length = 1, '', UPPER(Value[2:Length]))
END
You need to change it too:
IF Value[1] = '^' ! When the carat is the second character i.e. *^
CaseLess = 1
Value = UPPER(Value[2:LEN(Value)])
! Value = CHOOSE (Length = 1, '', UPPER(Value[2:Length]))
END
Seems to work for us and hasn't broken anything to our knowledge!
Today is April 27, 2024, 9:29 am This article has been viewed 35103 times. Google search has resulted in 27 hits on this article since January 25, 2004.
|
|