I'm within an "inch" of having ported my app from .NET to Flex/AIR. I have it working fine synchronously except for a problem refreshing the UI and getting the ProgressBar to work. So I wanted to try asynchronous mode. However, I cannot get either the errorhandler or the resulthandler to fire when the SQLStatement is executed! It's as if the eventhandlers aren't properly wired up. Any way to tell if they are, apart from placing a break-point inside the handler? The class attempting to do this work is a subclass of EventDispatcher. Are EventDispatchers not legal sinks for asynch data-connection events?
The connection is open. The database is running. The parameters are in place. I'm using event-driven pseudo-loops.
It should be working like a champ. But it's not even getting to first base.
Please see attached screenshot showing debugger values and code.
Ok, I've determined two things.
1. The handlers are correctly wired up.
2. The problems are not coding errors on my part.
I deliberately made a typo with one of the parameter names and the errorhandler fired. So we know it's wired up correctly and working.
I "cleaned" my project and then the result eventhandler fired! But I have to keep cleaning the project each time I run a debugging session or it won't fire the next time I try to debug.
Having success, and greater ease of debugging, when using Responders rather than Events with the async connection.