Technical Support Notes
| Article ID: | T26 |
| Date: | 5/7/99 |
| Product: | VB Guide 2.x (all versions up to and including v2.2.0) |
| OS: | Windows NT 4.0 |
| Problem: | Continuous rapid events causes error 32000 when some methods are executed |
Symptoms
Error 32000 occurs when events are continuously
sent from the controller and a method is executed, such as GetSPELVar.
Causes
A SPEL task is sending events continuously and SPEL
for Windows cannot send the command. For example, the following SPEL task is
rapidly sending events:
| Function main | |
| While TRUE | |
| SPELCom_Event 1000, "test" | |
| Wend | |
| Fend | |
The error 32000 in this case indicates that
SPEL for Windows could not send the command to the controller after several
attempts.
Remedies
Avoid sending continuous events. For example, if
you are sending up some kind of status, send the status only if it as changed.
Check the events from the controller by placing a Debug.Print
statement in the SPELCom_EventReceived handler. Maybe there is an error in your
SPEL program logic and SPEL is sending up more events than desired.
Run your VB project and check the Immediate window to view the events from SPEL and verify that the correct events are being received and that they are not continuous for long periods.
Status
This problem is being researched.
