Does anyone know of a way to have a VB executable running out of a Windows
NT Command file (.BAT) cause a "global" error
that NT would pick up as an ERRORLEVEL in a .BAT file?

RaiseError only seems to pop up a message box, causing the VB.EXE to end,
but checking  "ERRORLEVEL <> 0" on the
next line after the VB.EXE doesn't catch anything and the
bat file keeps chugging on.

Any ideas?

Thanks,
    John