I didn't say use OERN did I? I went back and re-read what I wrote, and sure enough, I didn't say anything about OERN.
You asked how to trap the error... that's using On Error GoTo ... NOT On Error Resume Next which ignores errors, and doesn't handle them or trap them... there is a clear difference between how OERN and OEGT work.

Something else that I just remembered... does this error ACTUALLY happen in the compiled version? Or is the ASSUMPTION that it will because it is happening in the IDE? I ask because there is a setting in the IDE that allows you to control how the IDE breaks for debugging when dealing with exceptions. It might be that you have Break on all errors, which I normally prefer, but in this case it may be giving a false sense of "OERN" not working. I don't have VB6 so I don't remember exactly where it is, but it's under a toggle menu item somewhere. I want to say that if you right-click in a code window, I think there is a toggle option... which expands out one or two more levels... you're looking for "Break on all errors" and "Break only on unhandled errors" ... it's that last one you really want.

But if this IS in fact happening in compiled code and not just in the IDE... beats me. I don't like OERN, so I don't use it, so I couldn't tell you.


-tg