Re: "Run-time error '50003': Unexpected error"

Kevin Provance

unread,

Nov 28, 2005, 3:46:46 PM11/28/05

to

I had this problem once before, but it was literally years ago. It involved
images as well. It had something to do with the image being invalid and
it's colour depth. I wish I could remember more.

It seems that it had something to do with those images not rendering
properly with users running 32 bit color.

My suggestion: Change the colour mode on your computer to different
settings and see if the error still occurs. it may be as simple as changing
the colour depth of your images...but this is just a guess based on what
happened to me back in 1997 or so.

- Kev

"Cornelius" <Corn...@discussions.microsoft.com> wrote in message
news:8AF906B8-F39E-4611...@microsoft.com...
> Starting an VB 6 compiled application on some computers causes the
> following
> error:
> "Run-time error '50003': Unexpected error".
> The first form is loaded correctly. Then somewhere in the unloading of the
> first form and the loading of the second one, the program crashes...
> I tried to following steps:
> 1. Installing the newest VB 6 Runtimes - no success
> 2. Trying to catch the error with "on error resume next" - no success, the
> application just disappears
>
> On some other pages, I found out that sometimes this happens when gifs are
> loaded. But I do not load any gifs. Only jpegs.
>
> Does any one have an idea whats happening here? I would be very happy if
> this annoying bug disappears :)
>
> Thanks a lot.
> Best wishes
> Cornelius

Cornelius

unread,

Nov 28, 2005, 4:25:06 PM11/28/05

to

Hi Kevin,

you were right. It's just the icon of a form that lets crash the whole
application... just mad...
thanks a lot.

Kevin Provance

unread,

Nov 28, 2005, 6:40:42 PM11/28/05

to

Glad I could help you out there bud. Post anytime...and keep on coding!
<g>

- Kev

"Cornelius" <Corn...@discussions.microsoft.com> wrote in message

news:3A72BC30-DCF7-44C6...@microsoft.com...

Mike

unread,

Dec 18, 2008, 8:45:01 PM12/18/08

to

Kevin --

I couldn't believe my problem was as simple as you suggested in your post
three years ago, so I first tried re-registering OCX files. That didn't work
but then I just tried changing from 16 color to 32 color and viola! Exactly
as you said.
Thanks!

Mike

MikeD

unread,

Dec 18, 2008, 9:26:02 PM12/18/08

to

"Mike" <Mi...@discussions.microsoft.com> wrote in message news:94FFC625-20F0-4527...@microsoft.com...

Except that you started a new thread (or it's been long enough that the thread has dropped from the server) and you quoted nothing. You're reply has no context whatsoever...so nobody has a clue what you're talking about.

--
Mike

Tommy Vinson

unread,

Jan 14, 2009, 7:32:00 AM1/14/09

to

sorry dudes, this wan't my problem.

Any other ideas for me?

C Kevin Provance

unread,

Jan 22, 2009, 7:35:04 PM1/22/09

to

I remember this actually. Glad it worked out for you. It took me forever
to track that bug back in the day. ;-)

"Mike" <Mi...@discussions.microsoft.com> wrote in message
news:94FFC625-20F0-4527...@microsoft.com...