General information
Category:
Forms & Form designer
>>I have a form with a big grid. When the user clicks on the grid, the click event has DO FORM myform WITH keyvalue. In the Init of the formset, there is a SEEK keyvalue. The formset has a nav buttonset with its own method which uses SKIP and SKIP-1 to see if it's at the beginning or end, in order to enable and disable the top, prev, next, and last buttons. Here's the maddening thing: when I run it in debug, it performs correctly, but when I run normally it doesn't land on the selected record. When I RESUME from the debug it misses. Then, of course, I can't see the code, but, in my debug window, I can see that the parameter was passed correctly. Any idea what's going on? When I used WAIT WINDOWs instead of the debugger, they told me the record was moved away from the one FOUND by the SEEK during the nav refresh. But when I put a WAIT WINDOW in the nav refresh code (in a class) it again worked correctly. How could use of the Trace window or WAIT WINDOWs affect SKIP?
>
>Are U using private data sessions? I had a really strange problem with 3.0 where a SET DATASESSION did not properly return focus. I dropped in a Wait window RECNO() timeout .25 and that seemed to correct the problem. I never investigated if 3.0b corrected the problem that I had. The user does not even notice the quick wait window. It is a work-around that wokred for me. htwh
I eventually figured out that I had conflicting CURSORSETPROP commands. It said one thing in code and another in my data environment. I don't know why, but when I removed the command from the code, the problem went away.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only