Set a default printer to LPT3 (AREV Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== Set a default printer to LPT3 (AREV Specific) ====
=== At 21 SEP 1999 09:00:57AM Tad Groves wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
We are using Arev 2.12 in a network environment and would like the default printer to be LPT3: instead of our local LPT1:.  We only use the LPT1: for certain reports because most of the reports require special paper(11x17).



I can do a SETPRINTER 3 at the TCL, but the users get tired of that.  



Who ever created our application has somehow hidden what starts our menu system.  I thought it was an RBasic program and made my modifications there.  This worked when I manually executed it, but I delete the object and this program and found that something else is executing our menu during startup.



Any suggestions are greatly appreciated.



tad.groves@nortonhealthcare.org

502-629-5531
</QUOTE>
----

=== At 21 SEP 1999 09:18AM Matt Sorrell wrote:  ===

<QUOTE>Tad,



One option is to add the SETPRINTER 3 command to the startup VOC.  This will automatically execute every time they log in and then they don't have to do it themselves.



Matt Sorrell

</QUOTE>

----

=== At 21 SEP 1999 09:29AM Tad Groves wrote:  ===

<QUOTE>What is the record I'm looking for.

</QUOTE>

----

=== At 21 SEP 1999 09:49AM Dale Walker wrote:  ===

<QUOTE>At the TCL f5 Edit VOC BATCH(for lack of a better name)

SETPRINTER3



Then go into Management, Users, Secure User and define the logon verb as "BATCH" for the respective users.



This way it will be automatic



Dale

</QUOTE>

----

=== At 21 SEP 1999 10:33AM Tad Groves wrote:  ===

<QUOTE>The original programmers working this application blocked account from seeing its configuration.  When I logged into sysprog and looked at the configurations I found the Logon Verb (as you knew I would).  Then I reran the application; modified the program that gets called from the Logon verb, with no change.  After stumbling around and breaking the Logon verb being used, I found a duplicate copy of the program that gets called from the Logon verb.  This program was hidden from me because right after the Account/User was started, it attached to a new directory for the programs and data which is where the duplicate and bogus called program resided.



Wow.  Everything is working correctly now.  Thanks for everyones input.

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=9A6209A835CF84E4852567F300477FBC|View this thread on the  forum...]]