Hi, thanks for the reply.
1. ASP does have On Error Resume Next. I have disabled this to see what
happens. Nothing happens.
2. No errors are being thrown in VB
3. Apartment threaded
I have the component running in the VB debugger and breakpoints in the
subroutine are not being trapped. Breakpoints in other routines are
consistently trapped.
After a bunch of tries, the breakpoint is trapped and the subroutine runs as
it should. Very wierd.
"Chris Barber" <ch***@blue-canoe.co.uk.NOSPAM> wrote in message
news:el**************@TK2MSFTNGP12.phx.gbl...
Do you have On Error Resume Next in the ASP?
Is the VB routine throwing an error.
Is the VB DLL compiled as 'Apartment Threaded' and 'Unattended Execution'?
How do you know that the routine is not being called? Have you run the DLL
in debug mode?
Chris.
"Michael Farber" <mf*****@iiac.com> wrote in message
news:Os**************@TK2MSFTNGP12.phx.gbl... Not sure if this is the right group for this but anyways...
I've got an ASP web application that uses a Visual Basic component to do
some work. I instantiate the component in asp and then attempt to call
the subroutine. The subroutine is actually invoked maybe 2 out of 10 times
run. What could possibly be the reason for this?? Why the inconsistency in
running the subroutine?
Cheers