title: Bizarre VB6 Make Problem - Previously working identical code won't recompile
body: <p>I've got a really strange error and any light that anyone can shed on this would be greatly appreciated.  </p>
  
  <p>I made some changes to some VB6 source which builds a COM object.  The automated build which builds our app returned an error.  No problem I thought--I'll just back out my changes.  Well <em>backing out my changes isn't making the problem go away</em>.  </p>
  
  <p>Specifically when I attempt to build the app via a .vbg file, with a command line like     <code>path\to\vb6\vb6 ProjectFile.vbg /make</code></p>
  
  <p>I get a message </p>
  
  <blockquote>
    <p>"Compile Error in File '', Line : Object library
    invalid or contains references to object definitions that could not be
    found."</p>
  </blockquote>
  
  <p>As I said, I reverted the source code so I'm really stumped as to why this error is still occurring.  Any VB6 gurus around who might be able to point me at an answer?  </p>
  
  <p>I can post the exact code in question but the fact that it was building correctly, stopped building correctly and now refuses to build correctly makes me think this is not a problem with my code but rather some problem in the environment.  Like something got put in the registry as a result of the previous build error.  </p>
  
  <p>Any tips, hints, or suggestions greatly welcome.  I realize my question is a bit sketchy but I'm not even sure what's important to include and what isn't. </p>
  
  <hr>
  
  <p>EDIT 1:</p>
  
  <p>Thanks for the excellent suggestions guys.  I think it is something to do with VB6 doing some sort of auto-registration.  </p>
  
  <p>Just to add a bit more detail: this problem does not occur when I build the referenced vbp file from the IDE.  It only happens on the make on the .vbg which contains the vbp.  Also the build tool in question automatically pulls latest source and the error happens on both my local box and the dedicated build box.  </p>
  
  <hr>
  
  <p>EDIT 2:</p>
  
  <p>Hi again all,</p>
  
  <p>The release engineering fellow figured out how to get this to build in his build environment so it's currently ok.  Once we're past this crunch, I'll try to interrogate him about what he did and share the details with everyone.  </p>
  
  <p>Thanks again for all the great suggestions.   This is what's so great about SO; that is, I asked about a 10-year-old technology and I got several great and on-point ideas.  </p>