Error '50003' Unspecified error in VB6 Program

1 Mar 2007 6:19 PM

albertleng

Hi all.

Hope you can help me on this.

I have a VB6 program in which i can run it successfully in WinXP PCs.

When i try to run the program in Win2000, the program cant be loaded
and shows "Error '50003' Unspecified error in VB6 program."

What i did was create a new VB6 program and load all the forms from
the previous faulty VB6 program into this new VB6 program with all the
codes copied also and this works... Why is it so as both programs are
the same?

Anybody has encountered this?
Please guide me.

Thanks a lot.

1 Mar 2007 7:05 PM

Kevin Provance

I've experienced this error before in regard to using high color images in
controls (picturebox for example) when the system was not set for it. I
reset my images for 256 colors and that seemed to clear it up. While this
may not be the cause for your issue, I do recall that error number being
involved with it.

Hope it helps.

- Kev

Show quoteHide quote

"albertleng" <albertl***@gmail.com> wrote in message
news:1172773146.525181.140920@30g2000cwc.googlegroups.com...
| Hi all.
|
| Hope you can help me on this.
|
| I have a VB6 program in which i can run it successfully in WinXP PCs.
|
| When i try to run the program in Win2000, the program cant be loaded
| and shows "Error '50003' Unspecified error in VB6 program."
|
| What i did was create a new VB6 program and load all the forms from
| the previous faulty VB6 program into this new VB6 program with all the
| codes copied also and this works... Why is it so as both programs are
| the same?
|
| Anybody has encountered this?
| Please guide me.
|
| Thanks a lot.
|

2 Mar 2007 6:03 PM

The Peasant

> I have a VB6 program in which i can run it successfully in WinXP PCs.
>
> When i try to run the program in Win2000, the program cant be loaded
> and shows "Error '50003' Unspecified error in VB6 program."

Your problem lies in one of the OCX files that are being accessed by your
program.
You will find that one or more of the OCX files are a different version on
the machine giving you the error message. In most cases, a newer version
than that used by the compiling machine will be ok, but not necessarily so.
I'm afraid no one else can tell you which OCX is causing the problem, but
use of a program like VBPowerwrap will wrap all OCX code within the finished
EXE and avoid problems like you have experienced.

The other thing that can happen is that if you sort out the OCX problem now,
the next time you install something new, eg a printer, it may update an OCX
silently and then you are left again with the problem of why your program
won't run any more.

Examples of some OCX's that may give you grief are comctl32.ocx,
comct232.ocx, tabctl32.ocx, msflxgrd.ocx, but there may be many more that
your program uses.
The Peasant