The error is from the VB virtual machine not from an API. I can't see how WinDbg would be useful on VB4 which is interpreted and is in P-Code.
Visual Basic run-time error 5 Indicates one of the following:
- An invalid collection or property name was entered.
- An out parameter was NULL.
- The value is not one of the supported values or falls outside the supported range.
- The property is read-only.
- The property cannot be changed after the object is created.
- An invalid index was entered.
And in case it's an API call VB uses LoadLibrary
and GetProcAddress
.
Some controls have lost default values over time and this can cause the first.
The third can happen if modern technology exceeds the program's expection, e.g. disk space.
Also see (sorry no links, they are on my hard disk)
Q131007 HOWTO: Use Windows NT WinDbg.exe with Visual Basic (it's for NT 3.5)
Q166275 HOWTO: Debug a Native Code Visual Basic Component in VC++ (talks about what you can see in VB in a debugger)
VB4 can't make symbols