I still need a bit more info on this. It's not clear to me what the
architecture of your project is. I am assuming that it is currently a
windows gui type app, that communicates with some other vb com objects (eg:
your "app object"). There is also some communication through interfaces... I
am assuming this is used to get the vb "poor man's polymorphism" of having
many objects implement the same interface (I use it myself, it's a nice
technique).

Could you outline the project architure in some detail? What are the
objects, and how do they call each other?

Also, very important is whether any back-end objects are exes or dlls (that
is, in-process or out-of-process), as they behave differently.

I am particularly intrigued by your need "to run multiple instances of the
program", and am assuming you want to do this "because we are trying to
modify parts of this to work on the web". If that's the case, you don't need
to be able to run any exes multiple times, you should just need to
instantiate objects multiple times. I'm unclear though as to whether this is
the path you are going down, so I'll wait to hear more.

Emlyn

> -----Original Message-----
> From: Dave Debreceni [mailto:ddebreceni@I...]
> Sent: Wednesday, 18 December 2002 0:22
> To: professional vb
> Subject: [pro_vb] RE: Automation Error
> 
> 
> Thanks for the response.
> The original programmer wanted to make things as easy as 
> possible, which ended up making things very difficult.  We 
> receive the automation error, which is all it says, does not 
> break or anything, when we try to run 2 copies of the program 
> at once on the box.  They have a main object called the app 
> object which has all of their base functions in it.  The main 
> class that they use is a global multi use class, and all the 
> data is accessed through this.  They use mostly interfaces to 
> communicate with items and most of the classes are set to 
> publicnotcreatable with the exception of a few that are 
> multiuse.  When I trace in it just happens that where it 
> errors is when it is trying to create an object that happens 
> to be multiuse. I am not sure whether the error is in our app 
> object or not, but I do know that if I stop the program when 
> it breaks that I get an automation error, but if I add the 
> app object as part of the project group this error no longer 
> happens in that circumstance.  I am really at a loss, because 
> we are trying to modify parts of this to work on the web, 
> however this error is holding us up.  Any suggestions on what 
> to try and look for would be great. 
> 
> Dave
> 
> -----Original Message-----
> From: Emlyn O'regan [mailto:oregan.emlyn@h...]
> Sent: Monday, December 16, 2002 8:21 PM
> To: professional vb
> Subject: [pro_vb] RE: Automation Error
> 
> 
> That interface looks very interesting. However, I don't think 
> the fact that
> it is IUnknown derived would be stopping you from running 
> multiple instances
> of your project. Can you provide more information on the automation
> error(s), and what you are trying to achieve?
> 
> Emlyn
> 
> > -----Original Message-----
> > From: Dave Debreceni [mailto:ddebreceni@I...]
> > Sent: Tuesday, 17 December 2002 0:26
> > To: professional vb
> > Subject: [pro_vb] Automation Error
> > 
> > 
> > Hello all,
> >     I have an automation error happening and I believe I have 
> > narrowed it down but want to confirm it with those who are 
> > greater than I.
> > The project I am working on, the original developer added a 
> > custom type library called ienumv.tlb.  This can be found on 
> > the web at: http://www.mvps.org/vbvision/Super_Collections.htm
> > The problem I think is that this custom library does not 
> > implement the IDispatch interface, rather just the IUnknown 
> > interface.  I unfortunately do not have access to the source 
> > of this type library, although I have asked for it.  What I 
> > need to know is if there is another way around this.  We need 
> > to run multiple instances of the program and this type 
> > library is causing an error.  If anyone has any suggestions 
> > they would be greatly appreciated.  Thanks.
> >  
> > Dave
> > 
> > 
> > 
> 
> 
> **************************************************************
> *************
> Confidentiality: The contents of this email are confidential and are
> intended only for the named recipient. If the reader of this 
> e-mail is not
> the intended recipient you are hereby notified that any use, 
> reproduction,
> disclosure or distribution of the information contained in 
> the e-mail is
> prohibited. If you have received this e-mail in error, please 
> reply to us
> immediately and delete the document.
> Viruses: Any loss/damage incurred by using this material is 
> not the sender's
> responsibility. Our entire liability will be limited to 
> resupplying the
> material. No warranty is made that this material is free from 
> computer virus
> or other defect.
> 
> 
> 
> 
> 
> 


***************************************************************************
Confidentiality: The contents of this email are confidential and are
intended only for the named recipient. If the reader of this e-mail is not
the intended recipient you are hereby notified that any use, reproduction,
disclosure or distribution of the information contained in the e-mail is
prohibited. If you have received this e-mail in error, please reply to us
immediately and delete the document.
Viruses: Any loss/damage incurred by using this material is not the sender's
responsibility. Our entire liability will be limited to resupplying the
material. No warranty is made that this material is free from computer virus
or other defect.