Hi, all!!!

My program running for several years now showed run-time error 66.
It is running far and not on my PC - I can't use a VB shell to check a line called an error...
I can't find error N66 number in error's list.
I see N63:Bad record number and next is N67:Too many files... :(

I have raised error N66 and it shows message:
'Application-defined or object-defined error'...

Also I use 'On Error GoTo ApplicationError:' to trap error in some subs (not in all).

Later in the same sub I put:
Exit Sub
ApplicationError:
TRACK_ERROR ("Sub: Form1/Form_Load()")

It seems I need to do that in each sub! Is it better way to do?

I also need to number lines via 10,20,30,40,50 and so on to know which line called an error exactly.

Is it all possible to be organized easier and better under VB6 ?
Code is very big, it is great job to put traps everywhere.
Is it possible to do just for one module and return absolute line number automatically when error is called?


Please reply - it is important to solve.


Alex

People, I have found answer quicker than anybody replied!

here is add-ins for VB6.

It makes most code automatically, it is simple and very good.
Use that and it solves all problems I was talking about...

http://www.sharewareplaza.com/AddErr...ads_13447.html



Alex