 |
|
 | C++ Event Trapping |  |
|
Moderator  
|
|
  |
||||||||||||||||
|
||||||||||||||||||
 |
| C++ Event Trapping | |
|
Moderator 
|
|
He's referring to the people on the other forum.
|
||||||||||||||
|
_________________ 
|
||||||||||||||||
|
| C++ Event Trapping | |
|
Moderator 
|
|
It's working! Mostly.
Then events are firing when I use a syncronous connection but not for asyncronous. Strange thing is that ADO appears to be waiting for the connection to be established before continuing. That kinda contradicts the point of an asyncronous connection. It is supposed to submit the open and continue on to the WaitForSingleObject. WFSO waits for the connect event to fire and then continues. If the event doesn't fire within a certain amount of time, an error is thrown. Now, why would it work for sync and not async? |
||||||||||||||
|
_________________ Sometimes you feel like a nut, and sometimes you don't.
|
||||||||||||||||
|
| C++ Event Trapping | |
|
Moderator
|
|
Ok, it does seem to fire the connect event while using an async connection but, not until I close the connection. That makes no sense.
As for the delay I'm seeing when I attempt to connect, I think that may be due to the network here or something they may be doing with the DB. |
||||||||||||||
|
_________________ Sometimes you feel like a nut, and sometimes you don't.
|
||||||||||||||||
|
 | C++ Event Trapping | |
|
||
|
|
|
|