Login | Sign Up
ErrorKey - Search engine for Error codes and messages     
  Visual Basic .Net:Visual Basic .Net Run-Time Messages  [ 296 result(s) ]
MICROSOFT 
 BC30753  -  Option Strict On disallows implicit conversions from '' to ''; the Visual Basic 6.0 collection type is not compatible with the .NET Framework collection type  MICROSOFT
Option Strict On disallows implicit conversions from '' to ''; the Visual Basic 6.0 collection type is not compatible with the .NET Framework collection type. The collection object that is used in Visual Basic 6.0 differs from the collection object that is used in Visual Studio 2008.
Explicitly convert collection objects by using one of the type conversion keywords. The CType Function and DirectCast keywords throw a run-time exception if the conversion fails. The TryCast keyword returns Nothing (Visual Basic) if the conversion fails.
Visual Basic .Net Compiler Messages
Comments
 
  -  Internal error in the Microsoft Visual Basic runtime  MICROSOFT
An internal error has occurred in the Microsoft Visual Basic runtime.
Note the circumstances under which the error occurred, and call Microsoft Product Support Services.
Visual Basic .Net Run-Time Messages
Comments
 
 BC30815  -  '' is not declared (Visual Basic Error)  MICROSOFT
Error Message '' is not declared. File I/O functionality is available in the Microsoft.VisualBasic namespace.
Use the file I/O functions defined in My.Computer.FileSystem, the System.IO namespace, Visual Basic run-time functions, or the Microsoft.VisualBasic.FileSystem object.
Visual Basic .Net Compiler Messages
Comments
 
  -  Internal error (Visual Basic)  MICROSOFT
An internal malfunction has occurred in Visual Basic.
Make sure this error was not generated by the Error statement or Raise method. Unless it was, contact Microsoft Product Support Services to report the conditions under which the message appeared.
Visual Basic .Net Run-Time Messages
Comments
 
  -  Out of stack space (Visual Basic)  MICROSOFT
The stack is a working area of memory that grows and shrinks dynamically with the demands of your executing program. Its limits have been exceeded.
Check that procedures are not nested too deeply. Make sure recursive procedures terminate properly. If local variables require more local variable space than is available, try declaring some variables at the module level. You can also declare all variables in the procedure static by preceding the Property, Sub, or Function keyword with Static. Or you can use the Static statement to declare individual static variables within procedures. Redefine some of your fixed-length strings as variable-length strings, as fixed-length strings use more stack space than variable-length strings. You can also define the string at module level where it requires no stack space. Check the number of nested DoEvents function calls, by using the Calls dialog box to view which procedures are active on the stack. Make sure you did not cause an "event cascade" by triggering an event that calls an event procedure already on the stack. An event cascade is similar to an unterminated recursive procedure call, but it is less obvious, since the call is made by Visual Basic rather than an explicit call in the code. Use the Calls dialog box to view which procedures are active on the stack.
Visual Basic .Net Run-Time Messages
Comments
 
  -  Out of string space (Visual Basic)  MICROSOFT
With Visual Basic, you can use very large strings. However, the requirements of other programs and the way you work with your strings can still cause this error.
Make sure that an expression requiring temporary string creation during evaluation is not causing the error. Remove any unnecessary applications from memory to create more space.
Visual Basic .Net Run-Time Messages
Comments
 
  -  The remote server machine does not exist or is unavailable (Visual Basic)  MICROSOFT
You are trying to connect to a remote server that is unavailable or does not exist. This error may be caused by your network connection being lost.
Reconnect to the network and try again.
Visual Basic .Net Run-Time Messages
Comments
 
  -  File not found (Visual Basic Run-Time Error)  MICROSOFT
The file was not found where specified. The error has the following possible causes: A statement refers to a file that does not exist. An attempt was made to call a procedure in a dynamic-link library (DLL), but the library specified in the Lib clause of the Declare statement cannot be found. You attempted to open a project or load a text file that does not exist.
Check the spelling of the file name and the path specification.
Visual Basic .Net Run-Time Messages
Comments
 
  -  Division by zero (Visual Basic Run-Time Error)  MICROSOFT
An expression being used as a divisor has a value of zero.
Check the spelling of variables in the expression. A misspelled variable name can implicitly create a numeric variable that is initialized to zero. Check previous operations on variables in the expression, especially those passed into the procedure as arguments from other procedures.
Visual Basic .Net Run-Time Messages
Comments
 
  -  Overflow (Visual Basic Run-Time Error)  MICROSOFT
An overflow results when you attempt an assignment that exceeds the limits of the assignment's target.
Make sure that results of assignments, calculations, and data type conversions are not too large to be represented within the range of variables allowed for that type of value, and assign the value to a variable of a type that can hold a larger range of values, if necessary. Make sure assignments to properties fit the range of the property to which they are made. Make sure that numbers used in calculations that are coerced into integers do not have results larger than integers.
Visual Basic .Net Run-Time Messages
Comments
 
 

 
Visual Basic .Net Compiler Messages (28)
Visual Basic .Net Run-Time Messages (268)
 
  Prev   1  2  3  4  5  6  7  8  9  10  Next