General information
Category:
COM/DCOM and OLE Automation
Title:
Problems with com-exe
I have created an application that creates a report with the help of an ocx (print engine). My customer has asked me if it´s possible to create a COM object that will enable him to generate the report on the web. For this I have created a COM-exe because the DLL seem to have a problem with the OCX. They refuse to do anything.
Running the COM-object from VFP6/7 works like a charm.
When calling it from VB6 I´m constantly seeing the message the connection to the COM-object is lost and if I want to retry it. The report is created.
When running the server with two instances of VFP I notice that the COM-object is not threading but the message never shows.
When both VFP and VB are running the COM-exe I get into trouble. What bothers me is that VB will constantly show a messagebox that the connection to the server is lost. The VFP session is blasting away but VB is constantly showing this message.
I have created a locking mechanism so I can avoid the two or more processes are generating the same document.
When calling the COM-exe from Internet Explorer nothing happens. I somehow get the feeling that the printerdriver that I want to use is NOT present.
What am I missing…are the printers available under IE? If not how can I force the COM-object to see the printer drivers. I need a postscript driver because I need to generate a postscript file that will be generated into a pdf-file with Acrobat Distiller.
How can I ´solve´ my two issues.
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only