OI & printer memory (OpenInsight Specific)
At 15 JUN 1999 05:31:04PM Bill Maher wrote:
When running reports from our OI 3.7 app my system (Pentium 350 with 64MB RAM) seems incapable of doing any other tasks. My printer is an
HP Office (inkjet) PRO 1175cse. I'm running Windows 98. I suspect that the lack of memory in my printer is bringing my system to its knees. Is there a recommendation for OI workstation printer RAM?
At 16 JUN 1999 06:30AM [email protected] onmouseover=window.status=why not click here to send me email?;return(true)", [url=http://www.sprezzatura.com" onMouseOver=window.status=Why not click here to visit our web site?';return(true)]Sprezzatura Group[/url] wrote:
Sounds more like the report process is not yielding to Windows. What are you using to report?
World Leaders in all things RevSoft
At 16 JUN 1999 09:17AM Matt Sorrell wrote:
Hmmmm, wonder what the answer will be if he's not using S/List???
At 16 JUN 1999 02:40PM Bill Maher wrote:
In this this case, just some Basic code. We are using S-List for some other reports. Yielding to Windows?
At 17 JUN 1999 03:41AM Oystein Reigem wrote:
Bill,
You have this function with a process running in a loop. Put a Yield() statement in the loop, and the system will at that point (I quote from the online help) check for pending events in the Windows event queue and execute them. Control is returned to your function as soon as the event queue is empty.
There's some pitfalls that you can read about in the thread http://www.revelation.com/WEBSITE/DISCUSS.NSF/f12696d31000b22a8525652b00831bb2/d3171c8fa7aa639a85256531002e0786?OpenDocument.
I have used it in cases where I want the user to be able to abort a process, typically a process like yours with a loop that reads one record at a time and does something with it. In the windows that run such processes I usually have an Abort button with a CLICK event that sets a global variable that the process can check. If the variable is set the process stops. But if it weren't for the Yield() the CLICK event would not run until after the process was finished. (Btw - if you ever try this - note that when you press the button it will not depress immediately. It will not seem to react until the Yield statement is run. So if your process takes a few seconds per record it may take that long between you press the button and you see any reaction.)
- Oystein -