Re: How would you handle this error 430 automation error?



Hi Michael,

I'd first clean the registry. If you have any existing dlls that are compiled you can do a simple regsvr32 /us dllname. Otherwise search the CLSID tree for your project component names/paths. (don't spend too much time on that though)

Next, open each project separately, set compatibility to binary and compile them. Store the dlls in the one output folder and add a reference to those dlls as needed in the toher projects instead of project references or project groups. Continue to compile.




"Michael Emerald" <MichaelEmerald@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:669AB0FD-C3B4-4CD5-8C25-C443B96D37AA@xxxxxxxxxxxxxxxx
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.

If you REALLY want to help, write me directly at westpointusma at yahoo dot
com. or, at least try to read my follow-ups. Much appreciated!

Michael Emerald
Longfellow Investments

.



Relevant Pages

  • Re: Non-compatibility of a VB6 dll although code unchanged
    ... > I carefully read your answer and the article about binary compatibility. ... > I compile my same code 2 times. ... Also, if the DLLs exceptionally large and contain large numbers of Publics, ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... So any VB6 successor is free to break compatibility to COM ... That doesn't imply that the "old syntax" couldn't be supported and that the new one couldn't support native code compilation. ... But I think it's a myth that you simply can take your native code and compile it to managed one and expect it to be the same as if you would re-engineer the whole application and rewrite it in .NET. ... But I also stated that this would break compatibility in many ways. ...
    (microsoft.public.vb.general.discussion)
  • GlobalMultiUse component breaks its compatibility !!!
    ... I have a component (ActiveX dll) with only one class in it. ... compiled, even though the binary compatibility is set, a new UUID is ... Public Property Let MyStringProp(ByVal vNewValue As String) ... Compile the project. ...
    (microsoft.public.vb.com)
  • Re: dependency scanner
    ... Ivy gave us a leg up on analyzing dependencies. ... Historically, this is done with configure, though ant ... packages that won't compile need to be skipped. ...
    (comp.lang.java.programmer)
  • Re: msvc*.dll loading
    ... It tells which versions of which DLLs your application depends ... but there is no manifest file in the ... (but i have seen this when i compile my real app). ... load CRT DLLs with LoadLibrary? ...
    (microsoft.public.vc.language)

Loading