I've got a very curious problem and want to know if anybody else has seen
something like that before and might have a hint.
Most times I try to compile my VB 6 project into an exe-file the whole VB
environment breaks up and it's thread is killed by windows. As result the
obj-files of the linking-step remain in the destination path of the
compilation. No error is coming up or logged.
I already installed SP 5 before. It's also curious, that the same code is
compiled successfully sometimes...

Q193000

----------------------------------------------------------------------------
----
The information in this article applies to:

  a.. Microsoft Visual Basic Learning Edition for Windows, versions 5.0, 6.0
  b.. Microsoft Visual Basic Professional Edition for Windows, versions 5.0,
6.0
  c.. Microsoft Visual Basic Enterprise Edition for Windows, versions 5.0,
6.0

----------------------------------------------------------------------------
----

SYMPTOMS
Attempting to compile a Visual Basic project residing on a network that only
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."

CAUSE
If there are N modules in a project, Visual Basic will create N + 1 object
files; one for each module and one for the project as a whole. The names are
derived from either the module name or, for the project, the EXE name. The
name used is either "<basename>.obj" or "<basename><number>.obj." A number
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, the
Visual Basic compiler/linker generates object files with the name
<projectname>1.OBJ when a conflict is detected, resulting in 9-character
filenames.

In a network environment that does not support long filenames, such as a
Novell network, the above error will occur.

RESOLUTION
Create shorter names for your form, module, and project so that if a name
conflict occurs, the appended number will not violate the short filename
requirement of your network environment.

STATUS
This behavior is by design.

--

Randy Birch
MVP Visual Basic
http://www.mvps.org/vbnet/
Please respond only to the newsgroups so all can benefit.

Make sure All modules (forms, classes, modules, usercontrols)
have OPTION EXPLICIT at the top.
Are you doing any subclassing/message handling?(might not matter)
How large are the individual code files, VB has a limit.
How many controls per form? VB has a limit.
Use any DLL's?  Addin's? (turn them off)

You can use #if to block out suspicious pieces

#Const RunThisCode = False
'#Const RunThisCode = True

Private Sub Form_Load()
  #If RunThisCode Then
    '...your codeblock here...
    MsgBox "Message Sent"
  #End If
End Sub

Then swap comments on the #CONST to try the compile
again (with the suspect code being back in), if it blows,
you've got your whale...  happy fishing!

D.

ale=ore;happy fishing=[fill in the blank]

I'm convinced that it wasn't setting the path to an absolute path that fixed
it: I'm fairly certain that just changing it caused it to work because if I
set it back to a relative path after switching it to an absolute path, it
still worked properly. In fact, IIRC, VB makes that change regardless.

Jason Bouzane