home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases
- Path: sparky!uunet!cs.utexas.edu!usc!sdd.hp.com!ux1.cso.uiuc.edu!news.iastate.edu!vincent1.iastate.edu!viking
- From: viking@iastate.edu (Dan Sorenson)
- Subject: FoxPro, printer not ready error trap
- Message-ID: <viking.711947974@vincent1.iastate.edu>
- Summary: How can I trap this thing?
- Keywords: help, trap, error, printer
- Sender: news@news.iastate.edu (USENET News System)
- Organization: Iowa State University, Ames IA
- Date: Fri, 24 Jul 1992 03:19:34 GMT
- Lines: 30
-
- I've a minor problem that's driving me crazy. I've an application
- that will list records to the HP LaserJet IIP on a 286 clone under DOS 4.01,
- and this printer is only 4ppm at best. So I collect the data, list it off,
- eject, collect more, list off, eject, etc... About ten pages into this
- dump the dreaded "Printer Not Ready" window comes up. I want to get rid
- of it and just let the thing sit in an idle loop until the printer is ready.
-
- I tried a simple loop like this:
- store .f. to canprint
- do while .not. canprint
- store printerstatus() to canprint
- enddo
- release canprint
-
- I think the function was printerstatus() -- it could be something
- slightly different. Anyway, it didn't work, and I got the window after
- ten pages again. This loop was placed right after the eject, and right
- before the list off, for what I hoped was maximum effect. The only
- other thing I can think of doing is writing my own error-handling routine,
- give an "onerr do myerror" and trap this error and then do the above
- routine. I'm not looking forward to this, though, since if I trap errors
- I had better trap them all! Ugh! There has to be a simpler method.
-
- Any ideas?
-
- <Dan Sorenson, DoD #1066 |"There'll be angels on Ariels in leather>
- <z1dan@exnet.iastate.edu | and chrome, Ridin' down from heaven >
- <viking@iastate.edu | just to carry me home." -- R. Thompson >
- < ISU thinks I need more education, which they provide for a fee. >
-
-