Serious SQLWindows BUG Alert!!!!!

In article <43ckmn$4k2@nntp.crl.com>, weiqigao@crl.com says... > >[We found a BUG in SQLWindows 5.0.1's SqlImmediate] > Some further comments (what I learned since I posted the article): 1. The SqlImmediate() in a Loop phenomenon I reported to the comp.adtabases.gupta internet forum is a BUG, recognized by Gupta in the (guess where) CompuServe Gupta$ Forum for quite some time now. Some of the posts there goes back to as early as three weeks ago. 2. The BUG is introduced in SQLWindows 5.0.1 . The program I posted in the last article works perfectly in SQLWindows 5.0.0. 3. The options we have are: Either go back to 5.0.0, --OR-- DON'T USE SqlImmediate() at all (use SqlPrepareAndExecute() instead) 4. I wish someone would have posted this bit of information in this news group earlier (at least that would save me five days of searching for a bug, a bug that happens after an extended preiod of running our programs, leaves no noticable trace, and crashes the Windows 3.1 system afterwards: --Come over here, Mike. --What? --I think I have found a bug. [Run app, push button, and wait for five minutes] --[The screen goes away.] Did you see that? --Yeah, I wonder what causes it. Let's do it again. Loop [Reboot, run app, push button, and five minutes later, boom!] ) 5. I'm cross-posting this article to other comp.databases news groups, in the hope of reaching the widest audience, and preventing someone else (like me) from the frustration that we have experienced (Something that Gupta should be doing right now.) 6. This sucks, big time! -- Weiqi Gao weiqigao@crl.com