title: How do I resolve "Run-time error '429': ActiveX component can't create object"?
body: <p>My company has a VB6 application using Crystal Reports 7 which a client has asked to be installed on Windows 7 32 bit. It is currently installed on Windows XP 32bit SP2 machines at the client. Connection to the DB is done via ODBC to SQL Server 2000 instance on another server.</p>
  
  <p>On Windows 7, the installation works fine, however when you try to open the application, the error is given.</p>
  
  <p>I have looked at the following:</p>
  
  <ul>
  <li>Registering all the dll's and ocx files using regsvr32. Some will not register as they either are registered already or the following message is given "Make sure that "[name].dll" is valid DLL or OCX file and then try again." I read this forum thread regarding this: http://social.msdn.microsoft.com/forums/en-US/vblanguage/thread/0653f685-4526-45d9-89f3-8c479a6b4c62</li>
  <li>Monitored the opening of the application using a ProcessMonitor application to try and spot if there is a missing dll or ocx file - this does not seem to be the case.</li>
  <li>Reviewed the application according to <a href="http://www.daniweb.com/code/snippet313435.html" rel="noreferrer">this list</a> and nothing seems to be against these guidelines</li>
  </ul>
  
  <p>I've noticed two items in the knowledge base that relate to this</p>
  
  <ul>
  <li>http://support.microsoft.com/kb/281848 - the comdlg32.ocx bundled with the application is version 6.0.81.69 and the one in the system32 folder on the dev machine (WinXP 32 bit) is 6.1.97.82. However if this was the issue then surely it would not work currently? </li>
  <li>http://support.microsoft.com/kb/184898 - I'm not sure how to confirm that this is the issue</li>
  </ul>
  
  <p>Finally, due to complexities, I am not allowed to make code changes to this application. Even if I was, I'm not a VB6 programmer, just the guy who got the terribly support project! If code changes are required, then I'll have to investigate using WinXP mode.</p>
  
  <p><strong>Update</strong>: I get the same error in XP Mode. That's a Win XP with SP3 VM. This runs on a Win XP SP2 VM, is there potentially something in SP3 that would have caused this to occur? Or is it just a fact of it being XP Mode?</p>