Delphi access violation in VB COM

[bhaisaab]

Hi,
I am facing a strange problem in Delphi. We have a COM component that does printing and we need it for high volume printing. When this is invoked from VB client (for test), it works fine. When run from Delphi client (which I need), in debug mode it sometime gives access violation in Winspool.drv. In run mode though, it just terminates abnormally without any message and the exe even vanishes from task manager. I am yet to figure out is this due to that print spooler can't handle the load, or is it related to Delphi's accessing COM.
If anyone has any suggestions, it will be very helpful

 

[buho]

I used to have the same problem with a program masivelly using the HINTERNET functions (winninet.dll).

The program worked fine for hours and days in 9x, but vanished without warning after some time (minutes to hours) running in NT/2K.

I've never found the solution, so I've dropped the wininet functions and implemented my own protocols.

My bet is about massive use of handles, but i have no facts to support it.

In your case it can be related to the COM object too. Some old COMs are somewhat ill-behaved (specially if designed for VB).

Sorry I can't help more.

buho (A).