 09-19-2007, 11:38
|
Nephilim2612
Joined on 06-19-2007
Posts 12
|
Programatically convert a document through ePrint API
|
  
|
|
|
Hello,
After searching through the forums i've not found an answer for the question i'm writing below.
I have to build a simple application (VB.Net, Visual Studio 2005, .NET Framework 2.0) using the ePrint API/COM in order to convert a DOC file to PDF through a Task Printer. This simple application will be helpful in order to decide whether to deliver or not a prototype for a possible client. Till here, all ok, i can even add a new task printer without nearly any difficulty.
The point is that, until now, i thought it was possible to, at some point, "give" the path to the document to convert to the ePrint API/COM and, thus, it(ePrint) should use or "take" the native application of the document and make the whole process or open the file and convert it to the destination format. But actually i have not been able to find the right place to do that. I thought that place was the parameter "DocName" of the EPrint.StartDoc method, but it seems to be rather the print job's name..
My first question is: whenever i want to programatically convert a file from one format to another by using ePrint API, must i manage the native application of the source file so i open the document and "order" that API to print it out to the desired task printer? Or is there a way to tell the ePrint API/COM: "ok, this is the path of the source document and this is the task printer i want to use, do it, please"?
My second question is: if the answer to the first question is "you should deal with the source doc's native app API", how do i programatically manage the JobInfo events then in order to, f.e, detecting when a print job has finished? Should i write the code dealing with Word, for example, between the StartDoc and EndDoc calls? (i've tried to do that but i still don't catch the events, even if i've set the EnableJobInfo property of ePrint to 'true')
Thank you very much
|
|
|
|
|
Report
|
|
|
|