Microsoft KB Archive/129895

= PRB: OPTION PRIVATE Statement Has No Effect in Visual Basic =

Article ID: 129895

Article Last Modified on 10/30/2003

-

APPLIES TO


 * Microsoft Visual Basic 4.0 Standard Edition
 * Microsoft Visual Basic 4.0 Professional Edition

-



This article was previously published under Q129895



SYMPTOMS
Using the statement Option Private when declaring a module does not affect the behavior of a Visual Basic version 4.0 application in any way.



CAUSE
The Option Private statement is not implemented in Visual Basic version 4.0. It is useful only in applications that support multiple projects loaded simultaneously and allow references between the loaded projects, as Microsoft Excel version 5.0 does for example. The statement makes it impossible to access members of the module from a referencing project even if the member is declared public.



STATUS
This behavior is by design. Because Visual Basic version 4.0 doesn't support multiple loaded projects, this statement has no use.

Keywords: kbprogramming kbprb KB129895

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.