How should I go about resolving this Error 430?

[westpoint]

Hello all.

I have a VB6 project with about 8 Classes in my IDE. I package the dependencies and notice that my Project references are not persisting. By iteration, I keep adding back the Project references, which in all cases are components I made. Then I package the dependencies, then I Package the executable for the project. I also get messages that certain dependency info is missing, in which case I browse or repackage the missing dependency, even if it's not presently in the IDE. Other missing dependencies relate to Excel.exe or something like that. The project runs fine in the IDE. But when I try to run Rita.exe (the project), I get a 430 automation error.

You can help me. What comes to mind are these possiblities:

1) That the fact that this thing doesn't compile quickly is indicative of the underlying problem. Meaning, that one of these non-persisting components and/or out of date dependencies (even though I repackage them) is the culprit.

2) That my compatibility is off. I always use Project Compatibility. Other programs I've developed have project compatibility and I recompile and deploy them all the time.

3) That somewhere I may have, by mistake, changed the interface in one of my classes. I doubt it, because I learned long ago not to do that.

So which would you do?
1) Start from scratch, copy to a new directory, give the classes and even executable new names, and recompile the brand new project?

2) Break compatibility? (if so, tell me how to do that)

3) Unregister the components in the registry? If so, can you tell me how to do that in a SIMPLE way?

It doesn't matter about old versions, sharing, etc. This is a small company and no one cares. I just want to get this thing deployed ASAP.

thanks.

[MartinLiss]

I'm not sure I can be much help but I assume from your post that you are not using a traditional installer like the P&D Wizard or Inno. Is that the case?

BTW you'll notice that I moved your thread.

[dilettante]

Maybe read Project Compatibility: Avoiding MISSING References?

You might also read through Using Binary Version Compatibility. It is not good to distribute components compiled with Project Compatability. Read this whole section.

Important: For the purpose of releasing compatible versions of a component, Project Compatibility is the same as No Compatibility.