PRB: Variable Not Defined Error Message When Using a ConstantLast reviewed: January 8, 1998Article ID: Q179027 |
The information in this article applies to:
SYMPTOMSThe following error message displays when you attempt to use a predefined constant for an automation server:
"Compile Error: Variable Not Defined"For example, you may receive this error when you try to use the constant xlR1C1 from the Microsoft Excel Object Library.
CAUSEYou are using late binding on an ActiveX component.
RESOLUTIONYou can use early binding by referencing the object library for the automation server in your project. Click References on the Project menu to select the object library.
Const xlR1C1 = -4150 STATUSThis behavior is by design.
MORE INFORMATIONLate Binding occurs when you declare a variable As Object, As Form, As Control, or As Variant and Visual Basic cannot determine at compile-time what sort of object reference the variable will contain. Therefore, Visual Basic must use late binding to determine at run-time whether the actual object has the properties and methods you call using the variable. Early Binding occurs when you make a reference to the object library at design-time. Visual Basic then knows what object library contains the properties and methods when you make your variable call. Early Binding also provides some performance gains.
REFERENCES"How Binding Affects ActiveX Component Performance" in the Visual Basic Component Tools Guide, version 5.0. Keywords : VB4ALL VB4WIN vb5all VBKBAX_VBKBComp kberrmsg Version : WINDOWS:4.0,5.0 Platform : WINDOWS Issue type : kbprb |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |