[AccessD] Print and listening to an IP address

Wortz, Charles CWortz at tea.state.tx.us
Fri Apr 18 08:10:22 CDT 2003


Mark,
 
 #1 Convert strPrintJob to a report and then set the default printer of
this report to the lan printer.
 
#2 Why do you want to listen for Ack/Nacks?  If the printer has a big
enough buffer for your report and the power doesn't go out, it will
eventually print the report.

Charles Wortz 
Software Development Division 
Texas Education Agency 
1701 N. Congress Ave 
Austin, TX 78701-1494 
512-463-9493 
CWortz at tea.state.tx.us 

-----Original Message-----
From: Mark L. Breen [mailto:subs at solution-providers.ie] 
Sent: Friday 2003 Apr 18 07:55
To: AccessD at databaseadvisors.com
Subject: [AccessD] Print and listening to an IP address


Hello All,
 
I have an application that previously printed to the LPT1 port on the
PC.  In my code, all I had to do was
 
Open "LPT1" For Output As #1
Print #1, strPrintJob
Close #1
 
We now want to use a new printer that is connected to the lan via an
ethernet card.  The printer is assigned an IP address and is listed in
the list of printers on my control panel.  It appears that it is not
possible to map my lpt1 to the printer.
 
What I think that I want to do is something like
 
Open 109.109.109.109 for output as #1
Print #1, strPrintJob
Close #1
 
So, question number one is "how to I sent text to an ip address"
 
 
I then had a serial communications piece of code that listened to the
serial port and was able to verify that what was sent to the printer was
received back.  I was able to listen to the buffer on the mscomm.ocx and
pass that back to the database.
 
So question number two is "how do I listen to an ip address to hear what
is coming from it"
 
Thanks in advance for your help, I know that this quesion is a bit
vague, but fire a few questions back at me if you wish.
 
 
Thanks
 
Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030418/68e3d247/attachment-0001.html>


More information about the AccessD mailing list