Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
BINDEVENTS & GPFs
Message
From
23/01/2008 16:27:09
 
 
To
23/01/2008 15:39:11
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows 2000 SP4
Network:
Windows 2000 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
01284697
Message ID:
01284737
Views:
14
This message has been marked as the solution to the initial question of the thread.
Just wanted to concentrate on this paragraph:

>In another instance, we noted that programmatic call to a CLICK event caused the GPF error to happen as well. In this case there was a directly seen call to the CLICK event, so the solution was to factor the code out of the Click to a method and have BOTH the Click event and the call to the Click event call the method instead. Because the click event was not called, the BINDEVENT code did not fire except one time, so the confusion was cleared and VFP ran as expected.


I've always understood the if you use Click() in code (which I assume is what you mean by 'directly seen call') all that you are doing is running the code contained in the Click() method - not raising the event itself. Are you saying that a call to Click() caused the BindEvent code to execute?

Should have prefaced this by stating by VFP is pretty rusty. Maybe someone else will clarify this...
Regards,
Vov
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform