PRB: Compile-Time Error Occurs Instead of Run-Time Error

Last reviewed: October 30, 1995
Article ID: Q129930
The information in this article applies to:
  • Standard, Professional, and Enterprise Editions of Microsoft Visual Basic, 16-bit and 32-bit, for Windows, version 4.0

SYMPTOMS

Setting a read-only property gives you a compile-time error instead of a run-time error. This behavior represents a new feature in Visual Basic version 4.0.

CAUSE

Visual Basic version 4.0 checks to see if read-only properties are being written to at compile time. That is why Visual Basic version 4.0 checks for this type of error when you select Make EXE File from the file menu, as opposed to just reporting the error at run time.

This also occurs when Running the program in the Design Environment (with Compile On Demand turned off). By using this new feature, the compiler prevents accidental writes to read-only properties. Having the compiler catch this type of error also stops the error from crashing a program during run time.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Start a new project in Visual Basic. Form1 is created by default.

  2. Place a Combo Box on Form1.

  3. Add the following code to the click event of Form1:

    Combo1.Style = 2

  4. Choose Make EXE File from the File menu.

  5. In the Make EXE dialog box, enter a name for your executable, and click OK. This results in the following error:

    Function call on left-hand side of assignment must return Variant or Object


Additional reference words: 4.00 vb4win vb4all
KBCategory: kbenv kbprb
KBSubcategory: EnvtDes


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 30, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.