error catastropic failure

dear all VB-lovers........
I had problems with my database program...... at error messages statement = catastropic failure......
any one can describe it ? how to make this failure does not comes out anymore.....
thanks for your times and willingness

use an error handler to trap the error, then handle it in an appropriate way

thanks but the problem is : that I don't know the cause or by what that "catastropic failure" appears or happens..... I also check to literatur....vb for programmers ....." on error code " chapter...... there is no further information about that failure.....
if I know what is the cause that failure or what the trigger (such as recordset conflict or connection conflict....or ?). I will know how to treat that errors..... any one can explain further information a:o bout "Catastropic Failure".....Thanks

Track down the issue, by placing a breakpoint close, there the error will happen, then press the F8 key as long as the error will appear. You can see what variables containing values, so you will find out what is causing the failure.

As the name stands for 'Catastrophic', the error should be a major (but unhandled) issue/error.

This may help
Get the Mztools vb addon and put line numbers in your subs then use:
On error goto e

e:
Msgbox "Error Number " & err.Number, "Error description " & err.Description & "Line number " & Erl

This may not work in your situation. if not i would put check points through out your code to determine where the problem is

Msgbox "Check one"
do stuff
Msgbox "Check two"
do stuff
Msgbox "Check three"
etc

guys.... I've solved the trigger which make catastropic failure.... many heads better than one head..... thanks guys......:D

Thanks for letting us know. You can help us now by pulling down the Thread Tools menu and selecting the Mark Thread Resolved item which will let everyone know that you have your answer.

the error : catastropic failure... that I've been through because of conflict adodb.recordset and dataenvironment recordset .... this is just my pre-asumption about this case ...... I'm not sure enough about exactly the cause that failure or maybe too early for me too judge the error from that I mention above...... perhaps some of senior vb programmer .... willing to confirm this case.... thankssss .... also I thank to all of you who had given advice to me ....

I haven't used the DataEnvironment before, but using two data access technologies at the same time is likely to cause various issues, such as locking and corruption. Getting an odd error (such as the one you got) is not entirely unexpected.

In this case both of your data access technologies are instances of ADODB, and I would normally assume that reduces (and maybe even eliminate) the chances for problems - unless the DataEnvironment modifies the objects in the connection/recordset collections (as it is bound, that is certainly possible!), in which case it would be much more likely to cause problems.

well.... thanks si_the_geek .... the best things that we can do is to minimize errors ....... and leave 10 % things that we didn't know, maybe more such as bugs and others...... heheheheh:thumb: