Seems to be printing month on the forum.

I was just wondering is I go to the printer definition (third page in) and in the close section of the printer process I put in a code of E (for execute) and command of PDISK PRN, will this automatically generate the pdisk prn command at the end of every print or will it have to still be called like a font type by my printing routine?

Also if I use it from the definition, are there any hidden pitfalls?

Of course the reason I need to use it, is so we don't get the old 45 sec delay using a Windows (Not Novell) environment.

TIA

CLaude

Suggest you create a subroutine

subroutine pdiskprn( LPT)

call setptr( LPT: char(0), 1)

return

where LPT is given values like "LPT1", "LPT2" and so on.

I hated the automatic routines released in ARev for printer control and just added this routine to the end of any processes where I needed to promptly release the printer. Also added a "Macro" key called "Release Printing" that executed above routine to default printer.

Dave

Claude,

I don't know the answer to your specific question, but did you know there is a registry setting you can modify to change the default print queue timeout in Windows?

Here is an article about the registry settings you can change.

[email protected]

Greyhound Lines, Inc.

Thanks Dave,

Always nice to learn things.

The printer definition never did call the routine at the close.

As I extensively used the Banded Report Writer for most of my many reports, and the thought of having to add a call to setptr after each call left me cold, so I renamed the Runreport VOC call to RR and redirected the Voc Runreport to this little routine.

I Assume the overheads are minimal - correct me if I'm wrong:

main.program.:

 declare subroutine catalyst

 B=@SENTENCE

 SWAP "RUNREPORT" WITH "RR" IN B

 CATALYST("X",B)

 call pp   ; *  where pp is my pdisk prn subroutine using setptr

return

Thanks again

Claude

Claude,

That should work just fine. Just keep in mind that if you ever upgrade your ARev version, your VOC changes could get stomped on.

[email protected]

Greyhound Lines, Inc.

View this thread on the forum...