Justin

In the error handler of your VB component you can reference the
mostly-undocumented feature Erl.  Use this code:
    lngErrorLine = Erl

Be sure to access this before your procedure or method loses scope (i.e.,
external function to log errors to NT Event Log, etc) otherwise Erl becomes
0 regardless of where the error occurred.

After grabbing the error line place it into Err.Source along with
Err.Source's original values then bubble up the error to ASP using
Err.Raise.
Just one example:
    Err.Source = Err.Source & vbCr & "Error at Line: " & lngErrorLine

Hope this helps.

Jason

Justin

If you don't already know, Interdev and the Visual Studio VB will also
work together for debugging. Make sure the dll isn't loaded into the
inetinfo process (restart if necessary), in VB make sure the project
settings are binary compatable, set a break point if needed, and do a
run with full compile (CTRL+F5). Then open the asp page. You
should then be able to step through the VB code in VB environment.

One gotcha is (under 2000, as far as I'm aware) is you need to
set IUSR_machinename access using dcomcnfg (run from the
command line, look under default security, then edit default access
permissions and add the IUSR_mn account. Don't do this on a
public access machine.

Rgds
Peter

In the error handler of your VB component you can reference the
mostly-undocumented feature Erl.  Use this code:
    lngErrorLine = Erl

Be sure to access this before your procedure or method loses scope (i.e.,
external function to log errors to NT Event Log, etc) otherwise Erl becomes
0 regardless of where the error occurred.

After grabbing the error line place it into Err.Source along with
Err.Source's original values then bubble up the error to ASP using
Err.Raise.
Just one example:
    Err.Source = Err.Source & vbCr & "Error at Line: " & lngErrorLine

Hope this helps.

Jason

try this:

Public Sub Main()
38  On Error GoTo err_handler
39  MsgBox "before"
40  MsgBox 1 / 0
41  MsgBox "after"
err_handler:
42  If Err.Number <> 0 Then MsgBox "Error in line " & Erl
End Sub

There are plenty of tools for line numbering. You can download a free one
with source code from my home page:
http://www.angelfire.com/home/dmzakharov/

Regards,
Dmitriy Zakharov.
Brainbench MVP for Visual Basic
http://www.brainbench.com

A few pointers for step through into VB COM objects from Interdev:

You need the server-side tools install of visual studio to get interdev to
do step-through debugging (disk 2 of 3).

There is a registry tweak to get the VB ASP Debugging process to appear in
DCOMCNFG. This is where you need to apply those security settings Peter is
talking about below.

Don't reference your COM object in Interdev's "Project references" section.
I have never got this to work. Interdev can step through into a (late-bound)
COM object without a reference. I think this is very clever - though I
expect there are some VB/system gurus out there who might assure me its all
very simple....

search the Microsoft Knowledge base for help on step through into VB Com
objects from interdev. Mail me if you need the registry tweak -

hope this helps

Ralph

For debug in ASP and Step into VB you need:
IE 4.0
NT 4.0 SP 4
MS Script De{*filter*}
Option Pack 4.0
IIS 4.0
Visual Interdev
FrontPage 2000 Server Extensions SR 2
--This seems wierd, but its the only way i could ever get
it to work flawlessly
--You also have to make sure that you have "run in
seperate memory space" selected for the web application
properties under IIS.  Also, when in interdev, select app
debugging check box under the project properties.  Once
you set your breakpoint in Interdev on the ASP code that
calls your object, you will step into your VB code.  Of
course you have to have that .dll open and running in VB.  
you can find more information in MSDN, but its outdated
and some of it doesn't work any longer.  The best case is
to just create a project group and simulate data passed to
your object from the second application.  That way you can
create easy testing scenerios.