This article was previously published under Q316010
You can build small Visual Basic projects successfully. However, if you build a large Visual Basic project, you may receive the following error message:
Could not execute 'C:\Program Files\Microsoft Visual Studio\VB98\Link.exe'
This problem occurs more often when you build your project under nested folders.
The length of the Link.exe command line exceeds the limitation of the operating system because of the large number of modules that must be linked in your project.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Visual Studio 6.0 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name Platform -------------------------------------------------------------- 8-Jan-2002 11:52 18.104.22.16845 1.601 KB VBA6.dll x86
To install this hotfix, rename the old VBA6.dll file, and then replace it with the new VBA6.dll file that is included in the fix.
If the number of modules in your project is not too large, you can build your project executable files into a folder with a short path such as C:\.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.