HELP - Error 50003 - VB5, Win 95, Win 98, Win NT

HELP - Error 50003 - VB5, Win 95, Win 98, Win NT

Post by Tammy Creb » Fri, 10 Dec 1999 04:00:00



Please HELP!

I have developed an application using VB5 EE SP3 on Win 95 and have updated
it using the same VB version on Win 98.  The application is installed at a
client running Win 95 and NT.

When compiling under Win 95 and running executable at client site on an NT
machine, I receive a run-time error 50003 regarding the use of GIF files.  I
don't use any GIF files or picture controls.  I had a problem with a newer
version of the common dialog control - VB5 on W95 thought it was a picture
box - but I thought I had corrected that.  I am also using Sheridan calendar
widgets v1.08 build 2.

Can someone help with this one???  I cannot reproduce the error on my W95 or
W98 machine.  Also, I would like to be able to compile on my W98 machine
referencing the W95 version of the necessary controls.  Any suggestions?

Thank you,

Tammy Crebo

 
 
 

HELP - Error 50003 - VB5, Win 95, Win 98, Win NT

Post by Jim Deutc » Sat, 11 Dec 1999 04:00:00


I've posted a very long list of possibilities quite a few times.  Search on
Deja for it, I don't feel like dredging it up again...especially to so many
newsgroups (note followups).

Jim Deutch
MS Dev MVP


>Please HELP!


 
 
 

HELP - Error 50003 - VB5, Win 95, Win 98, Win NT

Post by Dmitriy Briski » Wed, 09 Feb 2000 04:00:00


This error can occur when a component, referenced by your application,
installed at runtime is of an earlier version than the the one installed at
compile time.
Look at versions of COMDLG32.OCX and COMCTL32.ocx files on the computer
where the program was compiled and the computer where it gives the 50003
error.  I've had this happen to me and the reason was that I compiled my
program (in VB5) with version 6.x of these controls, but on the user's
machine those controls were version 5.x.  I believe it's a
bacward-compatibility problem of these 2 controls.  I solved this problem by
restoring the OCX's on my machine to 5.x versions and recompiling the
program with them.

Dmitriy


>Please HELP!

>When compiling under Win 95 and running executable at client site on an NT
>machine, I receive a run-time error 50003 regarding the use of GIF files..

 
 
 

HELP - Error 50003 - VB5, Win 95, Win 98, Win NT

Post by Leonardo Sartor » Tue, 28 Mar 2000 04:00:00



> This error can occur when a component, referenced by your application,
> installed at runtime is of an earlier version than the the one installed at
> compile time.
> Look at versions of COMDLG32.OCX and COMCTL32.ocx files on the computer
> where the program was compiled and the computer where it gives the 50003
> error.  I've had this happen to me and the reason was that I compiled my
> program (in VB5) with version 6.x of these controls, but on the user's
> machine those controls were version 5.x.  I believe it's a
> bacward-compatibility problem of these 2 controls.  I solved this problem by
> restoring the OCX's on my machine to 5.x versions and recompiling the
> program with them.

> Dmitriy


> >Please HELP!

> >When compiling under Win 95 and running executable at client site on an NT
> >machine, I receive a run-time error 50003 regarding the use of GIF files..

There I transcribe the information I took from MSDN about the 50003 error
(concerning GIF files)

FIX: "Unexpected Error" Message When Loading a GIF
Last reviewed: October 16, 1998
Article ID: Q194414

--------------------------------------------------------------------------------

The information in this article applies to:
Microsoft Visual Basic Learning, Professional, and Enterprise Editions for
Windows, version 5.0

SYMPTOMS

Loading a GIF file that does not specifically contain an Image Object into
Visual Basic 5.0 (for example, through the PictureBox control), generates the
run-time error 50003:

   "Unexpected Error"

CAUSE
Visual Basic 5.0 does not support GIFs that include images that are contained
within Application Blocks. The Image Object must be included in the GIF as a
separate Image Object.

RESOLUTION
Use one of the following methods to work around this problem:

Use Error Handling to trap for and handle appropriately error 50003 (unexpected
error) in your Visual Basic application. For more information, search for the
Help topic "Designing an Error Handler" in the Microsoft Visual Basic 6.0 Online
Documentation.
Ensure that images contained within a GIF file are included specifically as
Image Objects and not contained within Application Blocks.

STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the
beginning of this article. This problem was corrected in Visual Basic version
6.0 for Windows.

MORE INFORMATION
It is important to note that this error is somewhat of a "catch-all" error that
can be generated under other circumstances completely unrelated to the use of
GIF files. The purpose of this article is to provide details regarding one
particular set of circumstances where this error may arise.

As mentioned in the "Cause" section of this article, Visual Basic 5.0 does not
support GIFs that include images which are contained within Application Blocks.
The Image Object must be included in the GIF as a separate Image Object. This
functionality currently exists in Microsoft Internet Explorer 4.0 as well as
Visual Basic 6.0.

--------------------------------------------------------------------------------

Additional query words: kbVBp500bug kbVBp600fix kbdss kbDSupport kbVBp
kbErrorMsg
Version : WINDOWS:5.0
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS"
WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS
OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE
LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT
CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR
CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 16, 1998
? 1998 Microsoft Corporation. All rights reserved. Terms of Use.