Hello everyone,
When I error trap, I write out the module name and
procedure name. I always wanted to drill down one more
layer and write out the line that was executing in the
procedure when the runtime error occured. I've looked at
lots of line-type properties of the VBE object, but can't
seem to find the one I've described. Am I out of luck?
Thanks.
Geof.

You can number all your lines (no colons):
and display the error line using erl:

Sub LookHere()
100 a=5
200 a=6
300 On Error GoTo ErrRtn
400 msgbox 5/0 'gives an error
500 exit sub
ErrRtn:
Msgbox "Error in line " & erl
End Sub

"Geof Wyght" wrote in message
...
Hello everyone,
When I error trap, I write out the module name and
procedure name. I always wanted to drill down one more
layer and write out the line that was executing in the
procedure when the runtime error occured. I've looked at
lots of line-type properties of the VBE object, but can't
seem to find the one I've described. Am I out of luck?
Thanks.
Geof.

Hmmm... I had forgotten about line numbers. This means
that you have to number the lines. Perhaps one could just
number lines with a high potential to generate a runtime
error. Interesting...
Geof.
-----Original Message-----
You can number all your lines (no colons):
and display the error line using erl:

Sub LookHere()
100 a=5
200 a=6
300 On Error GoTo ErrRtn
400 msgbox 5/0 'gives an error
500 exit sub
ErrRtn:
Msgbox "Error in line " & erl
End Sub

"Geof Wyght" wrote
in message
...
Hello everyone,
When I error trap, I write out the module name and
procedure name. I always wanted to drill down one more
layer and write out the line that was executing in the
procedure when the runtime error occured. I've looked
at
lots of line-type properties of the VBE object, but
can't
seem to find the one I've described. Am I out of luck?
Thanks.
Geof.


.

Here's a bizzare solution:
1) Export the VBA code to a cls file.
2) Import the cls file to an Access table with an
autonumber field.
3) Export the Access table to a text file of some sort.
4) Import the text file into an Excel module.
-----Original Message-----
You can number all your lines (no colons):
and display the error line using erl:

Sub LookHere()
100 a=5
200 a=6
300 On Error GoTo ErrRtn
400 msgbox 5/0 'gives an error
500 exit sub
ErrRtn:
Msgbox "Error in line " & erl
End Sub

"Geof Wyght" wrote
in message
...
Hello everyone,
When I error trap, I write out the module name and
procedure name. I always wanted to drill down one more
layer and write out the line that was executing in the
procedure when the runtime error occured. I've looked
at
lots of line-type properties of the VBE object, but
can't
seem to find the one I've described. Am I out of luck?
Thanks.
Geof.


.

Geoff,
MZ-Tools has a (among many other very useful functions) a function which
will add line number to your code. http://www.mztools.com


Alex J


"Geof Wyght" wrote in message
...
Here's a bizzare solution:
1) Export the VBA code to a cls file.
2) Import the cls file to an Access table with an
autonumber field.
3) Export the Access table to a text file of some sort.
4) Import the text file into an Excel module.
-----Original Message-----
You can number all your lines (no colons):
and display the error line using erl:

Sub LookHere()
100 a=5
200 a=6
300 On Error GoTo ErrRtn
400 msgbox 5/0 'gives an error
500 exit sub
ErrRtn:
Msgbox "Error in line " & erl
End Sub

"Geof Wyght" wrote
in message
...
Hello everyone,
When I error trap, I write out the module name and
procedure name. I always wanted to drill down one more
layer and write out the line that was executing in the
procedure when the runtime error occured. I've looked
at
lots of line-type properties of the VBE object, but
can't
seem to find the one I've described. Am I out of luck?
Thanks.
Geof.


.

Thanks, Alex, I'll have a look at them.
-----Original Message-----
Geoff,
MZ-Tools has a (among many other very useful functions) a
function which
will add line number to your code. http://www.mztools.com


Alex J


"Geof Wyght" wrote
in message
...
Here's a bizzare solution:
1) Export the VBA code to a cls file.
2) Import the cls file to an Access table with an
autonumber field.
3) Export the Access table to a text file of some sort.
4) Import the text file into an Excel module.
-----Original Message-----
You can number all your lines (no colons):
and display the error line using erl:

Sub LookHere()
100 a=5
200 a=6
300 On Error GoTo ErrRtn
400 msgbox 5/0 'gives an error
500 exit sub
ErrRtn:
Msgbox "Error in line " & erl
End Sub

"Geof Wyght"
wrote
in message
...
Hello everyone,
When I error trap, I write out the module name and
procedure name. I always wanted to drill down one
more
layer and write out the line that was executing in
the
procedure when the runtime error occured. I've looked
at
lots of line-type properties of the VBE object, but
can't
seem to find the one I've described. Am I out of
luck?
Thanks.
Geof.


.



.