Create a table on the receipt printer computer that has a field in that is
checked by each computer that is assigned an ID (this has to be something
unique).  

Before sending the print job, the field is checked.  If blank, fill it in
with the ID.  When that succeeds, send the print job.  After the print job
finishes, clear the value from the field.  This way, if there is a value in
the field that is not the ID of the computer checking it, then it has to
wait until the field is cleared.

Sounds simple, but there could be issues that pop up, like what happens if
the network connection drops before a computer can clear the field?  Then
again, it might be worth checking into why the app as it is locks up if both
computers are accessing the one printer?  Is this a printer on the local
computer that is shared?  If it is, then the print jobs should be queued.
What OSes are involved?

John

-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Jeff Johnson
Sent: Tuesday, January 18, 2011 9:08
To: [email protected]
Subject: Re: Design Question

John:  It is 3000 and 1000 respectively.

Thanks,

Jeff

---------------

Jeff Johnson
[email protected]
(623) 582-0323

www.san-dc.com


On 01/18/2011 07:06 AM, John Harvey wrote:
> Check the time interval you specified. It should be in milliseconds.
>
> John
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On 
> Behalf Of Jeff Johnson
> Sent: Tuesday, January 18, 2011 6:56 AM
> To: [email protected]
> Subject: Design Question
>
> I have a remote computer that needs to start a job on the local 
> computer.  I have a form on the local computer that looks for 
> something to happen.  I tried changing a field in a table and set the 
> timer event on the form to three seconds.  This worked but took over 
> 30 seconds to start after the remote computer changed the value in the 
> field.  I changed the timer interval to one second and the timer never 
> fired.  I don't think this is the best way to do this.
>
> Any suggestions?  What I am doing is printing to a receipt printer 
> attached to the local computer.  Having both computers access the 
> receipt printer locks up the application on both computers.
>
> TIA
>

[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.

Reply via email to