INFO: How Visual Basic 4.0 Handles Files Marked Read-Only (143044)
The information in this article applies to:
- Microsoft Visual Basic Standard Edition, 32-bit, for Windows 4.0
- Microsoft Visual Basic Professional Edition, 16-bit, for Windows 4.0
- Microsoft Visual Basic Professional Edition, 32-bit, for Windows 4.0
- Microsoft Visual Basic Enterprise Edition, 16-bit, for Windows 4.0
- Microsoft Visual Basic Enterprise Edition, 32-bit, for Windows 4.0
- Microsoft Visual SourceSafe, 16-bit, for Windows 4.0
- Microsoft Visual SourceSafe, 32-bit, for Windows 4.0
This article was previously published under Q143044 SUMMARY
Visual Basic 4.0 may handle files with the read-only attribute set
differently than Visual Basic 3.0. This may result in a "Can't Edit Module"
error when trying to change a code module. The Visual Basic 4.0 development
environment will handle read-only files in one of two ways. The way Visual
Basic 4.0 behaves is dependent on the current setting of the ReadOnlyMode
property of the development environment. If the ReadOnlyMode is set to 0
(lenient) you will be able to edit files marked read-only just like Visual
Basic 3.0. Of course you will still not be able to save your changes. If
the ReadOnlyMode is set to 1 (strict) Visual Basic will not allow you to
edit files marked read-only.
Modification Type: | Major | Last Reviewed: | 12/9/2003 |
---|
Keywords: | kbenv kbinfo KB143044 |
---|
|