"patrickdrd " <pa********@dis cussions.micros oft.comwrote in message
news:7A******** *************** ***********@mic rosoft.com...
>I don't want to use that method,
I've already done that,
I want to print a label - ticket using more professional method,
I did something similar a few years ago for the mailroom department of a
large organisation. They had fairly complex printing requirements for labels
to go on outgoing documents and packages - barcode, postage paid mark,
reference number, address (obviously!) etc...
They had a small thermal printer for printing the actual labels, but wanted
the data to be entered and maintained on an intranet system. As Alexey
pointed out, ASP.NET cannot control a client printer, so we did the
following:
1) ASP.NET app for data input etc
2) SQL Server to manage the data
3) Dedicated PC with thermal printer attached
4) WinForms app installed on the dedicated PC which constantly "sniffed" SQL
Server for print jobs
5) Collection of Word templates with text tags e.g. <<barcode>>,
<<address>>, <<postmark>et c. When the users submitted a print job, they
specifiied the template to use and the WinForms app used Word automation to
create a new document based on the template chosen, substitute the text tags
with real data, and print the label.