The headings that should be invoked by .ColumnHeader don't always appear and using SortOnColumnClick (on a listbox) causes a run-time error.
Known bugs? Any way round them? Need to upgrade?
3 replies to this topic
#2
Joseph Bove
-
- Members
-
- 756 posts
ProIV Guru
- Gender:Male
- Location:Ramsey, United States
Posted 12 March 2007 - 05:46 PM
Stef,
Run-time error with Sort on column click:
Make sure that you are not doing any LSCALLs in the paging screen. An LSCALL will kill the session in 5.5
We've restructured a number of our screens to post to temp files before hand to get around any need for an LSCALL.
hth,
Joseph
Run-time error with Sort on column click:
Make sure that you are not doing any LSCALLs in the paging screen. An LSCALL will kill the session in 5.5
We've restructured a number of our screens to post to temp files before hand to get around any need for an LSCALL.
hth,
Joseph
#4
Donald Miller
-
- Members
-
- 205 posts
ProIV Guru
- Gender:Male
- Location:Cupar, Fife, Scotland
- Interests:Motorcycling, Running, Cooking
Posted 12 September 2007 - 07:28 PM
Hi Stef
Found some notes that said:
For Windows XP in a paging cycle:
.ColumnHeader must be set for all fields in the paging cycle
.SmoothModeSwitch must be set to TRUE for the paging cycle
and apparently
Clicking on a column header will re-execute the paging cycle with the appropriate sort key
But a logic search shows I'm not using it. The notes are maybe from tinkering around with VIP.
Found some notes that said:
For Windows XP in a paging cycle:
.ColumnHeader must be set for all fields in the paging cycle
.SmoothModeSwitch must be set to TRUE for the paging cycle
and apparently
Clicking on a column header will re-execute the paging cycle with the appropriate sort key
But a logic search shows I'm not using it. The notes are maybe from tinkering around with VIP.
Half of what he said meant something else, and the other half didn't mean anytthing at all
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
