Sequential S/Lists (OpenInsight Specific)
At 14 APR 2000 11:23:44AM Mark Plasko wrote:
I'm writing a stored proc that contains two conditional (If.. Then) clauses with each containing a S/List report for screen display. The reports works fine when one If Then argument is false, but if both are true, the first report displays properly and then immediately disappears as soon as the second S/List report is resolved.
I've tried inserting a message call between the If..Then clauses, but that only plops message and form on top of S/List report #1. Any suggestions on how to anchor a S/List report until the user is ready to see report #2?
I'm using the S/List2 evaluation copy and OI 3.7
Mark
At 14 APR 2000 12:26PM Oystein Reigem wrote:
Mark,
Perhaps it's the same as with Or_View - that it's not started modally, so it won't wait. See Carl Pates' posting . If I'm on the right track with this you need the handle to the S/List window.
- Oystein -
(PS. If you for some reason tries this with Or_View note the error Carl made in handle name (see follow-up postings).)
At 15 APR 2000 12:14AM Don Bakke wrote:
Mark & Oystein,
The solution is the same as OR_VIEW. However, it is not the S/List window that needs to be checked but the OIPI Preview form. The Window's class for it is THUNDERFORM (if memory serves) which is the generic class for many VB controls.
At 15 APR 2000 03:32PM Oystein Reigem wrote:
Don,
Thanks for that handle name. It might come in handy one day. I use OIPI too.
But it troubles me it's generic. What if there are other programs running, and some form of theirs has the same name? Then you might end up waiting for that other form instead.
- Oystein -
At 15 APR 2000 08:24PM Don Bakke wrote:
Oystein,
You can use the information Carl provided in the SENL article regarding FindWindow to distinguish between multiple windows using the same class.
At 16 APR 2000 02:49PM Oy2 wrote:
At 16 APR 2000 03:03PM Oystein Reigem wrote:
Don,
Thanks. I found what you're referring to in S/ENL Volume 2 Issue 2.
I actually came across this problem last year, with a third party program having a generic class name. It was a program we bought for use together with our app. I got the programmer to change the class name. He was game, even if the program wasn't at all made particularly for our app.
I'll remember to use Carl's method next time!
- Oystein -