Thanks for all of your help. This works quickly and perfectly:
When the remote computer processes a sale a file is created on the
local computer named receipt.chk and drawer.chk (which prints a receipt
and opens the cash drawer if cash sale).
On the local printer there is an invisible form with a timer on it
(set to 2 seconds) that checks for the existence of the files.
When the timer fires, runs a program that returns immediately if
those files don't exist.
If they exist, they are printed and the files are deleted.
Jeff
---------------
Jeff Johnson
[email protected]
(623) 582-0323
www.san-dc.com
On 01/18/2011 11:06 AM, Jeff Johnson wrote:
> Hey Dan! You understand the problem perfectly. The receipt printer is
> working fine and has for several years. The problem is printing to it
> from a workstation. My solution is for the remote computer to tell the
> local printer to print the remote's receipt. I have it working, I just
> need to speed it up.
>
> Thanks,
>
> Jeff
>
> ---------------
>
> Jeff Johnson
> [email protected]
> (623) 582-0323
>
> www.san-dc.com
>
>
> On 01/18/2011 11:01 AM, Dan Covill wrote:
>> Hi, Jeff
>>
>> I'd guess your problem is that the "receipt printer" uses a parallel
>> connection, which is why you're still using @say's and also why you have
>> to use the "local" machine. I've just been through all this with a
>> client who uses multi-page forms on a couple of Okidatas.
>>
>> 1. You don't have to use @say's. A parallel port appears as LPT1: (or
>> alternatively PRN:), so your code probably looks like:
>> set device to print
>> @say........
>> @say........
>> set device to screen
>> This directs the @say lines to the (old) parallel port, or LPT1:
>> But you can also generate a plain text file, and then just
>> copy temp.txt to LPT1:
>>
>> 2. The real problem is that no new computer has a parallel port. We
>> finally bought a "dongle" that connects the printer's parallel
>> connection to the office router. But now we're not using LPT1:, and
>> both VFP and Windows start diddling the output, so we had to use the
>> RawPrint package (on the ProFox downloads), which worked just fine.
>>
>> Dan Covill
>>
>> On 1/18/2011 7:27 AM, Jeff Johnson wrote:
>>> Thanks for the info. The problem is that it is a receipt printer and
>>> you have to print to it using @say's. I will try your suggestion and
>>> see how it goes. Thanks
>>>
>>> Jeff
>>>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
