🚀 go-pugleaf

>it prints elsewhere.  So this is not a case of choosing printers, I need
>to make it work with the long printer name.  Any suggestions?

Map the printer to a local port.
__
Bowen Moursund (TeamB)
bowen at nerds dot com
http://lonestar.texas.net/~moursund/
Try this help resource:
http://www.dejanews.com/home_ps.shtml

Bowen Moursund (TeamB) wrote:

>
>
> Map the printer to a local port.
> __

I do not know how to do this.  I checked out the dejanews but do not have a
clue. This is on a Win95 machine.  I did install the printer driver with the
capture to LPT2 port for DOS programs, but this did not help.  So is this
something else to try?

>
> Bowen Moursund (TeamB)
> bowen at nerds dot com
> http://lonestar.texas.net/~moursund/
> Try this help resource:
> http://www.dejanews.com/home_ps.shtml

Thank you.

Bowen Moursund (TeamB) wrote:

> >> Map the printer to a local port.
> >> __
> >
> >I do not know how to do this.  I checked out the dejanews but do not have a
> >clue. This is on a Win95 machine.  I did install the printer driver with
> the
> >capture to LPT2 port for DOS programs, but this did not help.
>
> On the Details tab of the printer properties dialog, click 'Capture Printer
> Port...' and proceed. After mapping the printer to a local port, set the
> printer to print to that local port.
> ____
> Bowen Moursund (TeamB)
> bowen at nerds dot com
> http://lonestar.texas.net/~moursund/
> Try this help resource:
>  http://www.dejanews.com/home_ps.shtml

>> Map the printer to a local port.
>> __
>
>I do not know how to do this.  I checked out the dejanews but do not have a
>clue. This is on a Win95 machine.  I did install the printer driver with
the
>capture to LPT2 port for DOS programs, but this did not help.

On the Details tab of the printer properties dialog, click 'Capture Printer
Port...' and proceed. After mapping the printer to a local port, set the
printer to print to that local port.
____
Bowen Moursund (TeamB)
bowen at nerds dot com
http://lonestar.texas.net/~moursund/
Try this help resource:
 http://www.dejanews.com/home_ps.shtml

"Bowen Moursund (TeamB)" wrote:

>
> On the Details tab of the printer properties dialog, click 'Capture Printer
> Port...' and proceed. After mapping the printer to a local port, set the
> printer to print to that local port.
> ___

I have tried the above solution and put the line
    'Set printer to "LPT2"'
in my setup code.  But I still have the problem.  The program does not load.
This is not failing to print; just not loading until I change the defalt print
to one with a shorter name.  It almost seems as if d-base is looking for a
printer before it loads the program into memory to find out that I want it to
print to the port.  (Does that sentence make sense?)  So my users at the remote
location can use the program, but do not like having to switch printers.  They
keep forgetting and send stuff here.

>I have tried the above solution and put the line
>    'Set printer to "LPT2"'

That command is unnecessary, and may be part of the problem. Use
ChoosePrinter(), or set the system memvar _pdriver in code. If the .INI of
the app has a printer section, remove it.
__
Bowen Moursund (TeamB)
bowen at nerds dot com
http://lonestar.texas.net/~moursund/
Try this help resource:
http://www.dejanews.com/home_ps.shtml

It still does not work.  Just for fun, I changed the printer at my location.
It had been a port mapped to a printer, so I took the port out of the
picture--just the printer.  Now I tried to load Visual dBase.  I got the same
error msg.  So I put the port back in(sounds like too much wine to me) and
dBase loads.  My guess it is dBase is looking for the default printer when it
loads and if it is longer than 31 characters, it won't load.  The remote
machine now has the printer mapped to a port but dBase won't load.  There is
no reference to a printer in my .ini.  If this is not in my .ini, where is
it?  Crystal Reports?

Just out of curiosity, have you checked to see which printer is the Windows
default?  I've mapped printers just the way everyone suggested in 5.6, and
it works for me.

John

--
Staub & Associates, Inc.
(850) 913-8488
http://www.staubassociates.com
Buy books, music & video online
at http://www.staubassociates.com/bkstore.htm
Peggy Harp wrote in message <369A84A9.F6628622@muhlenberg.edu>...
>It still does not work.  Just for fun, I changed the printer at my
location.
>It had been a port mapped to a printer, so I took the port out of the
>picture--just the printer.  Now I tried to load Visual dBase.  I got the
same
>error msg.  So I put the port back in(sounds like too much wine to me) and
>dBase loads.  My guess it is dBase is looking for the default printer when
it
>loads and if it is longer than 31 characters, it won't load.  The remote
>machine now has the printer mapped to a port but dBase won't load.  There
is
>no reference to a printer in my .ini.  If this is not in my .ini, where is
>it?  Crystal Reports?
>
>
>
>

John Staub wrote:

> Just out of curiosity, have you checked to see which printer is the Windows
> default?  I've mapped printers just the way everyone suggested in 5.6, and
> it works for me.
>

This is how the users get the app to load--they switch from their local printer
to mine.  By switching, they make mine the default.  Then the app loads fine.

This morning I made the off-site printer my default printer.  When I tried to
run dBase, it would not load.  Same error message--the printer name is longer
than 31 characters.  I do not know if this helps but I am using networked
printers, using Win95 and 3.1 machines and Novel 2.0.

Peg,

  I may be wrong here, but this is how I've done it in 5.6.  If the user has
a local printer that is used in the app, I have them set this printer as
their Windows default printer.  When they are working in Word, Excel, or any
other app and send a document to the printer, they "select" the appropriate
network printer.  It is a bit of a pain, but it works.

John

--
Staub & Associates, Inc.
(850) 913-8488
http://www.staubassociates.com
Buy your books, etc. online at
http://www.staubassociates.com/bkstore.htm

Peg Harp wrote in message <369AB3F0.9EFABAC5@muhlenberg.edu>...

>This is how the users get the app to load--they switch from their local
printer
>to mine.  By switching, they make mine the default.  Then the app loads
fine.
>

John and Bowen,
Since you both have said mapping the priter should work, I went back to the
printers to check on their mapping.  Sure enough, both were not mapped to a
port.  Even though I had added the printer and 'captured printer port' during
the add printer, it had not done it. The path to the correct printer was not in
the list of ports to choose.  I then captured again, this time it appeared in
the list.  This seems to be working. It appears this is something in the
network.  I will not know for sure if it 'holds' until all gets rebooted
tomorrow when the system is again brought up.  Strange.  Thanks for your help.

John Staub wrote:

>
>
>   I may be wrong here, but this is how I've done it in 5.6.  If the user has
> a local printer that is used in the app, I have them set this printer as
> their Windows default printer.  When they are working in Word, Excel, or any
> other app and send a document to the printer, they "select" the appropriate
> network printer.  It is a bit of a pain, but it works.
>

John, this is what I have been having them do. But they were still having
printing problems and blaming it on my app.  Not only that, the reports from my
app were printing here instead of there.

Peg,

  Let us know.

John

--
Staub & Associates, Inc.
(850) 913-8488
http://www.staubassociates.com
Buy your books, etc. online at
http://www.staubassociates.com/bkstore.htm

Peggy Harp wrote in message <369B8D97.2B77B79C@muhlenberg.edu>...
>John and Bowen,
>Since you both have said mapping the priter should work, I went back to the
>printers to check on their mapping.  Sure enough, both were not mapped to a
>port.  Even though I had added the printer and 'captured printer port'
during
>the add printer, it had not done it. The path to the correct printer was
not in
>the list of ports to choose.  I then captured again, this time it appeared
in
>the list.  This seems to be working. It appears this is something in the
>network.  I will not know for sure if it 'holds' until all gets rebooted
>tomorrow when the system is again brought up.  Strange.  Thanks for your
help.

Peggy,

> I do not know if this helps but I am using networked
> printers, using Win95 and 3.1 machines and Novel 2.0.

PMFJI. I missed the earlier part of this thread, so I don't know if
we're talking VdB 5.x or VdB 7.x here. But,<g> my 'official' product
documentation (the shrink-wrap box<g>) for VdB 5.x states for supported
networks:

Novell NetWare 3.11, 3.12, 4.1, and Personal NetWare

and 'official' product documentation (the shrink-wrap box<g>) for VdB
7.x states for supported networks:

Novell NetWare 3.12

I coulda sworn VdB 7.x was also certified on NetWare 4.x, but I don't
see any indication of it.

BTW, if you don't like my 'official' version of the docs, if 5.x, take a
look at the ReadMe.TXT file in the \VisualDB home directory where the
same is echoed there. If 7.x, it's not in the ReadMe.TXT file, and I
couldn't find it in the online help, but I'm sure I've seen it elsewhere
as well.

IAC, 2.0 sounds like a rather old version, if memory serves. Was that a
typo? If not, you may not be able to resolve this issue without a
NetWare upgrade.

Or, if I've missed the whole point of the problem, then...never mind!<g>

Hope it helps.
-- 
Jim Sare - TeamB
-----------------
Some useful information, files, and links at:
http://home.att.net/~jimsare

Jim,


>
> IAC, 2.0 sounds like a rather old version, if memory serves. Was that a
> typo? If not, you may not be able to resolve this issue without a
> NetWare upgrade.
>
> Or, if I've missed the whole point of the problem, then...never mind!<g>
>

Actually, it turns out that it is Novel causing the problem.  And 2.0 is not
a typo--wish it was.  However, two tech guys from the IT dept spent the
better part of this afternoon scripting logon stuff to get the printers to
work more reliably with Win95.  They gleefully(my own interpretation<g>)
told me that they do not support dBase.  However, in order to get the
printers to work with their networked stuff, they had to get it to work with
my app.

Peg Harp, amateur programmer, full time registrar