"Tony Gravagno" wrote
Quote:
randy.cathcart wrote:
In some situations I capture the print job# at creation
Ya know, that's a good idea too. I don't recall offhand if mvBASE has
a SYSTEM() param to get the most recent spooler entry number like D3.
But you can capture that number, save it, and present the user with
their own personal list of print jobs by name rather than number. I
never thought about doing this but it seems like a great way to manage
reports without forcing any user to go through the spooler mechanisms.
T |
Tony... your instincts are correct...
In fact the MvBase doco shows a wide variety of Mentor-like SYSTEM()
options.
To wit: SYSTEM(102) returns the spooler entries currently in use, by 'print
file' number, separated by CHAR(254) with null values representing currently
available print file numbers.
Also of note: System(48) & (49) which are 'Name of this Network Node' and
'Number of this Network Node' respectively; and System(57) 'Console
process#' where '-1' = none active.
B-