At 01:49 PM 9/14/2002 EDT, you wrote:
>In a message dated 9/14/2002 12:59:36 PM Eastern Daylight Time,
>[EMAIL PROTECTED] writes:
>
><< CVAL('CurrentPrinter') doesn't give you the default printer. It gives you
> the current printer which may or may not be the designated default printer.
> >>
>Bernie, that's very true. It does give you the current printer. And in
>Windows, the current printer IS the default printer.
Damon -
Under W2K, IT IS NOT. I checked this out before I posted the original
message. Is it different under another Windoze version? The following
is relevant to W2K only.
If you use PRNSETUP to change to a printer other than the Windows default
printer then the CurrentPrinter will be the printer you have changed to;
however, the Windows default printer will be unchanged. To verify this
do the following:
1) Start > Settings > Printers Note the Windows default printer
2) Use PRNSETUP to change the current RBase printer to a printer
other than the Windows default printer.
3) At the R> prompt test (CVAL('CurrentPrinter')) It will return the
printer you selected with PRNSETUP.
4) Start > Settings > Printers Note the default printer. It will be
unchanged from step 1 and CurrentPrinter is not the Windows
default printer. QED
>
>Do a PRNSetup, choose a printer, and then open your printer folder, and it
>will show the one you have set in PRNSetup as the default printer.
No it doesn't. It shows the default printer I set with Windows printer
properties.
>exit out, reboot the operating system, it will still have the last printer
>set as the default printer.
Not on my machines - assuming you mean set with PRNSETUP. The default set
using the Windows options will persist through reboot.
>
>So the only way I see it to work is to capture the default printer
>when you come into the system, or change your code everytime someone changes
>the default printer. To me, ANY hard coding default printers is a pain in the
>neck, and a maintenance nightmare.
The first thing my users do in a network situation is choose the printer
they want to use for RBase with PRNSETUP. That way the desired printer is
set from the beginning. If someone else changes the default printer at the
print server or wherever it doesn't matter.
>To make things a LITTLE easier, code the printer names in a table, then
>choose the printers from there, with a default printer for each machine, then
>you might be able to maintain it.
I would rather use PRNSETUP because that offers the users the printers
that are currently available.
>A PrnSetup when you come into the system, so the user can choose their
>default printer when they start RBase might work. But then, you have the
>situation where the user has to be able to pick the default printer. That
>works as long as the RBase user is sophisticated enough to choose it, but I
>certainly wouldn't want my shop floor people doing it.
My shop floor people are sophisticated enough to choose among the printers
they should be using.
>Then you could set the default printer var, choose the one your using, then
>back to the default. However, we're back into the situation where another
>program may be looking for the default printer that IT had set, so it's
>another Catch-22.
What you seem to be saying is that PRNSETUP changes the default printer on
the machine/network. I don't think it can. I believe the Windows default
printer remains the same even when PRNSETUP is used to change the RBase default
printer.
Bernie
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/
