In my little programm I am reading a excel-sheet and visualize it in a
list. It runs very nice. After I deploy it the programm wouldn't start. In the errorlog is the following entry: {079802D0: cf 079802B5, sp 079802E0, bp 079802CC, ip 5, AXTypeLibraryAnalyzer(Object)>>doesNotUnderstand:} receiver: a AXTypeLibraryAnalyzer arg[0]: Message selector: #addGlobalToPackage: arguments: a Array But I unchecked every option that smells like it could lead into stripping out anything. Has anybody an idea? |
Is the stripping of the development system the reason why the executeable
fails? In the class-comment someone can find: AXTypeLibraryAnalyzer is primarily intended as part of Dolphin's development environment... |
In reply to this post by KlausK
"KlausK" <klaus.kirchhoff@munge> wrote in message
news:[hidden email]... > In my little programm I am reading a excel-sheet and visualize it in a > list. > It runs very nice. > After I deploy it the programm wouldn't start. In the errorlog is the > following entry: > > {079802D0: cf 079802B5, sp 079802E0, bp 079802CC, ip 5, > AXTypeLibraryAnalyzer(Object)>>doesNotUnderstand:} > receiver: a AXTypeLibraryAnalyzer > arg[0]: Message selector: #addGlobalToPackage: arguments: a Array > > But I unchecked every option that smells like it could lead into stripping > out anything. > > Has anybody an idea? I think it would be helpful if you posted more of the error log. The prime question here is why is it trying to call that method. A stack trace should answer that questions. Chris |
Hi, thanks for answering.
The method is called because I tryed the deploy something like the Excel example3. At execution time there is no Excel class and in that example the programm tries to build it up and put it in a package. This fails because most of the used Methods of that path are 'development' parts. They aren't in the deployed executeable. The result is this complaining. - that is what I found out till now. I think I have to use a different way to talk with Excel before I am able to deploy it again. Cheers Klaus |
"KlausK" <klaus.kirchhoff@munge> wrote in message
news:[hidden email]... > Hi, thanks for answering. > The method is called because I tryed the deploy something like the Excel > example3. At execution time there is no Excel class and in that example > the programm tries to build it up and put it in a package. This fails > because most of the used Methods of that path are 'development' parts. > They aren't in the deployed executeable. The result is this complaining. - > that is what I found out till now. > I think I have to use a different way to talk with Excel before I am able > to deploy it again. Yes, if you are referring to AXTypeLibraryAnalyzer class<<example3 that does seem to include an example of how to programmatically generate the interface classes. If you let it generate the interface wrapper classes in your development image, and then deploy it (without the regeneration of the interface wrapper classes) it might work. If you really do not want to generate the wrapper classes then see IDispatch class<<example3 for an example. However I tend to think that it is better to generate the wrapper classes. There is also a UI based wizard you can use to generate the wrapper classes. See the "Tools/Additional Tools/Active-X Component Wizards" menu item. You may need to make some modifications to the generated code. You might do a Google Groups ( http://groups.google.com ) search, I think using Excel from Dolphin has been discussed a few times in the past. Chris |
Thank you for trying to help me.
I think I am stupid. After all I found out that the example generates the wrapper-classes, like you decribed. All I had to do is referencing this new classes instead of those from the development package. The second was, I had to prevent the Excel and co. classes from beeing stripped. So at the end all works fine! Thanks again Klaus |
Free forum by Nabble | Edit this page |