Home > Archive > Clipper > December 2005 > Re: Clipper,ADS,Terminal server,OTC,Georgia Telnet Server and so
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: Clipper,ADS,Terminal server,OTC,Georgia Telnet Server and so
|
|
|
| Hi Marcello,
>
> OTC has a product named TERMINAL
> Did somebody have already used it with ADS?
>
....
>
> How is printing locally with both these two products?
>
With OTC Terminal you have several possibilities of printing.
1. Automatic mapping of LPT1-LPT3 server ports to respective
terminal machine ports. You don't need to change your app at all.
2. There is an API allowing your CLipper app to access WIN32 printing
functions on server, so you can define remote printers on Windows
level and use them via this api.
3. You can prepare server file containing your printout and call
function TrmFlPrint("filename",LPTPORTNUM) which will transfer your
file to the terminal machine and print it on the specified LPT port.
4. You can prepare server file containing your printout and transfer
it to the terminal machine using TrmPutFile(filename) function.
Then you can link your custom printing procedure into our terminal
emulator (te.exe) and call it from app using TrmTrmRPC function.
The procedure should open a transferred file and do whatever
appropriate on the terminal machine. The averall process looks
like this:
* preparing server file myprintout.txt
....
* tranfsering file to terminal machine
TrmPutFile("myprintout.txt","myprintout.txt")
* calling your custom terminal-side procedure
TrmTrmRPC("MYPRINTPROC","myprintout.txt")
Regards,
Jacek
|
|
|
|
|