Discussion Locked

VB 6 installed on Win2k on P4

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Having recently upgraded my hardware to a P5 running win2k, I am know finding several annoyances with VB6 Enterprise Edition. The main one is that when you compile a project it always wants to place it on your C: drive under visual studio. Previously using VB6 on NT4 Service pack 6A, once you compiled a project to your desired location, every time you compiled it after then, it went to your desired location. On win2k it always reverts to c:\program files\visual studio\vb98

3 replies

by andrew

I'm using VB6 on Win2k on a P5 and don't have this problem.

The build path is saved in the project file. After you do a build, save the project and open the VBP file in notepad. Look for the 'Path32' setting. If it is missing, then the executableis built to the project folder.

If you need to, you can manually put a 'Path32' setting in the file, pointing to where you'd like the executable to reside.

by adym

Tried this but to no effect.
HAve resorted to manually confirming file locations when compiling files

This discussion is closed to new replies.