- Microsoft Visual Basic Unexpected Error 50001
- Microsoft Word Visual Basic Unexpected Error (50001)
- Microsoft Visual Basic Unexpected Error 50001 Mac
Microsoft Visual Basic Unexpected Error 50001
-->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.
The statement is syntactically complete, but an additional programming element follows the element that completes the statement. A line terminator is required at the end of every statement.
A line terminator divides the characters of a Visual Basic source file into lines. Examples of line terminators are the Unicode carriage return character (&HD), the Unicode linefeed character (&HA), and the Unicode carriage return character followed by the Unicode linefeed character. For more information about line terminators, see the Visual Basic Language Specification.
- Hav you Googled this? I get a large number of hits and I'm sure there's one there to help you. Even the registry is mentioned. I mean, you're not telling much in your post, it's like me phoning the doctor and say 'it hurts here' and he cannot see me.
- Error 50001 problems include computer crashes, freezes, and possible virus infection. Learn how to fix these Microsoft Excel runtime errors quickly and easily!
- Regarding the phrase 'unexpected error', I agree this sounds like a tautology, but it is not really. VB can raise errors in situations which are expected e.g. When a file is missing. These are 'expected errors' and should be handled by specific code.
Error ID: BC30205
To correct this error
Microsoft Word Visual Basic Unexpected Error (50001)
Check to see if two different statements have inadvertently been put on the same line.
Insert a line terminator after the element that completes the statement.