This article was previously published under Q193000
This article has been archived. It is offered "as is" and will no longer be updated.
Attempting to compile a Visual Basic project residing on a network thatonly supports 8.3 filenames may generate the following error:
"fatal error C1083: Cannot open compiler generated file: '[path to file]\[projectname]1.OBJ': No such file or directory."
If there are N modules in a project, Visual Basic will create N + 1 objectfiles; one for each module and one for the project as a whole. The namesare derived from either the module name or, for the project, the EXE name.The name used is either "<basename>.obj" or "<basename><number>.obj." Anumber is added if the base names of the N + 1 files have naming conflicts(such as test.bas and test.frm).
Therefore, even if the project name may be fewer than 8 characters, theVisual Basic compiler/linker generates object files with the name<projectname>1.OBJ when a conflict is detected, resulting in 9-characterfilenames.
In a network environment that does not support long filenames, such as aNovell network, the above error will occur.
Create shorter names for your form, module, and project so that if a nameconflict occurs, the appended number will not violate the short filenamerequirement of your network environment.
This behavior is by design.
For additional information, please see the following articles in theMicrosoft Knowledge Base:
152789 : HOWTO: Install Visual Basic to a Network Using 8.3 File Names
191902 : PRB: Errors Using Setup Wizard on Novell Network
Microsoft Visual Basic 5.0 Learning Edition, Microsoft Visual Basic 6.0 Learning Edition, Microsoft Visual Basic 5.0 Professional Edition, Microsoft Visual Basic 6.0 Professional Edition, Microsoft Visual Basic 5.0 Enterprise Edition, Microsoft Visual Basic 6.0 Enterprise Edition