- Post your sample codes here so that we can give you a solution to your problem: ) Hi, I am trying to open the form from the project explorer ( Visual basic 6.0 ). Double clicking on a particular form ( frmDispatchEntry ) I am getting the:. RUN-TIME ERROR 50001. UNEXPECTED ERROR; QUITTING.
- I have a Access.mdb application with its modules written in VB and protected with a password. When I attempt to open a module to view the code to make changes.
- In control panel, go to system Advanced system settings Advanced tab Performance settings advance change Virtual memory. Then select custom size and increase it to a reasonable amount of value. Initial size 8000, Maximum Size 15000. Click ok and restart the computer to make the change.
- Microsoft Word Visual Basic Unexpected Error (50001)
- Microsoft Visual Basic Unexpected Error 50001 Mac Word
- Microsoft Visual Basic Unexpected Error 50001
The Microsoft Visual Basic Unexpected Error (50001) on Mac occurs when using Microsoft Word. In most cases, the error pops up whenever the Word app is opened.
Thanks to all the replies and previous post about the elusive Error 50003unexpected error. We got this error while trying to load the first form of
the application, and it would hose up memory. Worked fine on Win98 and NT,
and seemed to work OK on Win95 with Office97.
Microsoft Word Visual Basic Unexpected Error (50001)
We tried all the ideas about comctl32.DLL, OCXs, GIFs (as described on the
microsoft web site for this error code). Still did not work.
We were finally able to isolate it down to the form graphics (jpegs). It
only happened on the test machines which had low end video cards, and we had
256 color jpeg graphics. The reason Office97 made it work was that when it
runs the Office Assistant it loads DIBENG.DLL into memory. Yamaha yts 62 serial number. Which as I
understand is a 'device independent bitmap' graphics engine/driver.
Our solution was to save our graphics as DIB files, which when loaded
automatically loads the DIBENG.DLL and the graphics are automatically set
according to the video capability.
Thanks agian for all the great ideas! We were really stumped and all your
ideas helped us to forge ahead and focus on some areas until we found the
culprit. THANKS!
> Help!
> I am trying to run my VB application on a Win95 machine, but get this
> error
> [Run-time error '50003' Unexpected Error]
> just before loading the first form. Using display messages debug, it > displays the mesages just prior to loading the form, but not the first
> message in the open form event. (I am displaying message boxes because
> the app runs fine on my NT development PC, but not on the user Win95
> PC).
> Overall, the app runs fine on an NT or Win98 machine, seems to be OK on
> a Win95 with Office97. But certainly does not run OK on a Win95 without
> Office.
> I've tried isolating missing DLL and OCX files to no avail. Any other
> ideas? Also, after installing memory monitor the app ran OK, too.
> Unfortunately the users can not have Office97 or other extraneous files
> loaded. I need to isolate the specific file incompatibility or
> whatever.
> Your help is much appreciated! Please reply to my e-mail as well as the
> group.
> Jeff Bryant
Tutak tutak tutiya english subtitles download.
Unexpected Error 50003 - This is a good one!
Microsoft Visual Basic Unexpected Error 50001 Mac Word
Unexpected Error 50003 - This is a good one!
Microsoft Visual Basic Unexpected Error 50001
This is the problem explained in some detail below:
I run a VB 5 exe on a Citrix server (NT) which is accessed by the user via thin client technology. I have the source code on my laptop (Win98) which is where i do all my developing of code, I also compile the code on my laptop and then update the server with the new exe as and when needed.
The problem i am having is recently, when i amend code and compile the exe on my laptop and then copy it over to the server - the exe runs fine but certain forms within the application when attempted to be accessed throws up the error below which is then handled appropriately within my code (ie chucks me out to main MDI form without causing a fatal error):
50003: Unexpected Error
The thing that really gets me is that if I point the ODBC connection on my Laptop to the live d/base and run the exe on my Laptop everything runs perfectly and all forms can be accessed! So i can't even re-create the error on test in order to debug it thoroughly ..... Another thing as well - if i revert back to a previous exe the forms within the application which cause the error, open perfectly with no errors on the server - help!
The only thing which has changed over the last few months is that our company has changed from a Novell network to a MS exchange network, so I have a sneaking suspicion it is a Dll, Ocx version problem between the server and my laptop??
Thanks in advance, Chris