In situations like this I have sometimes discovered that it is better to
use On Error Resume Next despite the fact that it bloats up the code.
It allows for more specific error messages.

-----Original Message-----
From: Charles Feduke [mailto:webmaster@r...]
Sent: Wednesday, April 25, 2001 4:22 PM
To: professional vb
Subject: [pro_vb] Re: Error Info


    Take a look at this month's Visual Basic Programmer's Journal for
the black
belt programming column (or something to that effect).  It tells you how
to use
symbolic debugging information to debug a Visual Basic executable.
Pretty good
article.

- Chuck

----- Original Message -----
From: "Raheem" <raheem@f...>
To: "professional vb" <pro_vb@p...>
Sent: Wednesday, April 25, 2001 2:02 PM
Subject: [pro_vb] Error Info


> Is there any way in VB6 to know which line (line no/module name/form
name
> etc)of the code has generated the error? (like it was possible in
Clipper)
>
> Thanks