|
-
May 22nd, 2001, 05:08 AM
#1
Thread Starter
Member
-
May 22nd, 2001, 06:15 AM
#2
Fanatic Member
Components
You will need to be more specific than you have (for my benefit anyway).
How are you passing an object reference from one application to another? Are they ActiveX EXE's?
If you could explain that in more detail then it might be clearer what's going on.
-
May 22nd, 2001, 06:44 AM
#3
Thread Starter
Member
Ok,
To start, I made a shell environment (normal exe) that acts like an empty box.
The only thing it does is open an application, (Passing neccesary parameters to that application) the application is an ActiveX DLL.
One of the parameters I pass to that object is the object that generates that error. That object (activeX DLL, I call him the objShell) is like an interface between the shell and the application.
If an application needs to open an other application he passes the objShell to that new application. So the new application can communicate with the shell also.
That is offcourse not the only thing it does.
Every application asks to that objShell its other neccesary arguments.
This was until now no problem.
The case now:
I open through the shell an application A. In application A I open
an new application B. B gets the objShell from A. At the point that A wants to pass the objShell to B he generates that error.
Code:
In application A:
appB.oShell = objShell
In application B:
Public Property Let oShell(ByRef value as object)
set objShell = value
End Property
The threading model is Single treaded.
Every application is an ActiveX DLL.
I hope that is sufficient.
THANKS
VB, C/C++, ASP, HTML, Javascript, Java, SQL, VB.NET
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|