How to find out what is causing that annoying DX8 error.

[XerShade]

Okay so I was getting this on my client for some reason and I did the following to see what was causing it.

**Instructions:**

1) Goto Tools -> Options in the menu bar of VB6.

2) Select the general tab.

3) Set error trapping to ALL.

Should look like this:

[attachment=273:FixDX8.png]

4) Re-run the client and see what the duck is going on.

I was surprised to see that an EQUIPMENT subscript was giving me a DX8 error, thanks for making me waste an hour playing the code to try and fix it whoever wrote that useless handler.

[tslusny]

Wow great find xD

[abhi2011]

Gives me an error in InitDX8 which is obv wrong 

[XerShade]

> Gives me an error in InitDX8 which is obv wrong 

Hence why I said this handler is useless, error handlers should REPORT what went wrong, not just exit out and ignore it.

[abhi2011]

Error handler during runtime where never designed to show the line of code that crashed.

During runtime a small lightweight version of debugging is built thats all.

[XerShade]

> Error handler during runtime where never designed to show the line of code that crashed.
>
> During runtime a small lightweight version of debugging is built thats all.

My main point is that error handlers should NEVER be used to "Ignore" errors like some people do,