title: 'File Not Found: VBA6.dll' Error - Strange Behaviour
body: <p>I am running Windows 8 with Office 2013 (64-Bit). I am trying to continue developments in VBA in Excel that I started with Office 2010 (32-Bit). I am aware of the necessary 64-Bit alterations however I am receiving confusing configuration errors.</p>
  
  <p>Here is the problem:</p>
  
  <ul>
  <li>If I create a new Excel file and VBA project; all my VBA code functions correctly. No problems.</li>
  <li>If I open and use a macro from a file that was developed/used in Office 2010 previously, I receive a "File Not Found: VBA6.dll" error message.</li>
  <li>Once I start receiving the message, I receive it on all VBA macro's; even the new ones that (not more than 30 seconds) previously worked fine.</li>
  <li>If I then re-create a new Excel file and new VBA Project, that individual piece of new code works fine. No problems - until I run code in one of the 'error files'. The fault then spreads into my new developments.</li>
  </ul>
  
  <p>It's as if Excel is getting its references confused but every time I check them (on good or bad files) they are always exactly the same.</p>
  
  <p>Note:</p>
  
  <ul>
  <li>None of my references are missing.</li>
  <li>I don't have VBA6.dll on my system; I have VBA7 and the 'Visual Basic for Application' reference refers too 'C:\Windows\SysWOW64\msvbvm60.dll'</li>
  <li>There are two other 'Visual basic for Application' references on the list but it wont let me change them</li>
  <li>It works on new files without VBA6.dll so I assume it isn't required?</li>
  <li>I have checked for and installed all the latest Windows updates.</li>
  </ul>
  
  <p><strong>What should I do to troubleshoot this problem?</strong> </p>
  
  <ul>
  <li>If you think I need VBA6.dll, is that because the referenced libraries use it? </li>
  <li>If so then why are they not using VBA7? </li>
  <li>And why does it work correctly before opening an old VBA6 file? Does Excel suddenly decide all files must use VBA6 just because one file did previously?</li>
  </ul>
  
  <p>Anything to cure me of my confusion is much appreciated,</p>
  
  <p>Best regards</p>
  
  <p><strong>EDIT:</strong> I almost forgot to mention;</p>
  
  <ul>
  <li>When I try to debug the error after receiving it, Excel crashes (every time).</li>
  <li>I also sent a 'bad file' to a colleague who [with the same system configuration] hasn't yet received this problem - and they also received the error. Suggesting it is something wrong with the files?</li>
  </ul>
  
  <p><strong>EDIT 2:</strong></p>
  
  <p>The problem is not yet resolved. I hope the downvote will not hinder my chances of an answer.</p>
  
  <ul>
  <li>I have also tried re-registering libraries but nothing has changed.</li>
  <li>If I open a 'bad file' I can add new Macros and they work fine; but the second I run an existing Macro and receive the error, the new Macros do not work either.</li>
  </ul>