Well, I wrote a small test app and do a bit of my own stress-testing. It seems to be working as it should. Every call that I did got throw the SQL event as it should.
Yeah, It was definitely something with what I did before. --- In [email protected], "jason_williams_mm" <jwilli...@...> wrote: > > Have you logged a bug? Intermittent issues are very hard to track down. > What platform are you using (windows, OS X, Linux)? What version of the > runtime? > > Thanks, > jw > > > --- In [email protected], "handitan" <handitan@> wrote: > > > > Hi all, > > > > I posted this question quite a while ago but I just want to bump this > > thread up to see if anyone has any idea of the issue that I am facing. > > Please read below. > > > > Thx! > > > > --- In [email protected], "handitan" <handitan@> wrote: > > > > > > Hi all, > > > > > > Before I present the issue, I am listing my FB and SDK versions: > > > - FlexBuilder 3.0.2 > > > - AIR SDK 1.5 > > > - Flex SDK 3.3 milestone build. > > > All the latest good stuffs. > > > > > > Now, I have an issue with DB that's connected asynchronously doesn't > > > ALWAYS firing SQLEvent.RESULT or SQLErrorEVENT.ERROR whenever a SQL > > > statement is executed. > > > > > > For example: > > > I got a login screen with login textInput, password textInput, and login > > > button. When the login button is clicked, it does a query to check > > > whether the login and password exist in the DB. > > > And events will be fired accordingly if it's a success or not. > > > > > > HOWEVER, the events don't always fired! Sometimes it fires but sometimes > > > it's not. It's happening intermittently. > > > > > > Does anyone else have this issue?? > > > > > > Btw, I don't have this issue at all when I have my DB opened > > > synchronously. Unfortunately, working with it has some big challenges as > > > well. So if I can get the DB-async to work properly, it will save a lot > > > of time. > > > > > > Thx! > > > > > >
