 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
VB Forum / COM / March 2004Type Mismatch on Creating reference to shared Object
I have an ActiveX Exe component that has a singleuse object One of the reference to this object is created in the client application, the other reference is created at the bas module in the Exe_server itself For some reason I keep getting the "Type Mismatch" error when creating a reference to this singleuse objcet from the client app It is not even a consistent error because sometimes the client app is able to create the reference without any errors. This is the case when I am using both the client and Exe_server in the debug mode (i.e separate instances of VB IDE However when I try to use the compiled version of the client with the compiled executalble of the Active Exe_server, the error is consistent. The client is never able to create a reference to the singleuse object. I get the same "Type Mismatch" error all the time The shared reference to the singleuse object is exposed by pointing all the reference to a global variable declared in the bas mod of the Exe_Server Has anyone come across this problem? Is this a bug in VB that I am unaware of thank rc Do you have Binary Compatibility set up correctly? Binary Compatibility http://www.vbsight.com/BinaryComp.htm > One of the reference to this object is created in the client application, the other reference is created at the bas module in the Exe_server itself. Also, this reference in the bas module may cause the activex exe to not shutdown correctly. It'll only shut down when all references are released (including internal references)  SignatureKen Halter - MS-MVP-VB - http://www.vbsight.com Please keep it in the groups.. > I have an ActiveX Exe component that has a singleuse object. > One of the reference to this object is created in the client application, the other reference is created at the bas module in the Exe_server itself. > For some reason I keep getting the "Type Mismatch" error when creating a reference to this singleuse objcet from the client app. > It is not even a consistent error because sometimes the client app is able to create the reference without any errors. This is the case when I am using both the client and Exe_server in the debug mode (i.e separate instances of VB IDE) > However when I try to use the compiled version of the client with the compiled executalble of the Active Exe_server, the error is consistent. The client is never able to create a reference to the singleuse object. I get the same "Type Mismatch" error all the time. > The shared reference to the singleuse object is exposed by pointing all the reference to a global variable declared in the bas mod of the Exe_Server. > > Has anyone come across this problem? Is this a bug in VB that I am unaware of? > > thanks > rc Binary Compatibilty was the culprit for the Mismatch error. But seems like that is not the only problem Now for some reason I am not getting Event Notification from the COMPLIED Active X Exe component with the client in either the compiled or debug mode. But if I run the Exe component in separate instance of VB and then run the client, it does receive the Event Notification.any suggestion thanks ke r ----- Ken Halter wrote: ---- Do you have Binary Compatibility set up correctly Binary Compatibilit http://www.vbsight.com/BinaryComp.ht > One of the reference to this object is created in the client application, the othe reference is created at the bas module in the Exe_server itself Also, this reference in the bas module may cause the activex exe to not shutdow correctly. It'll only shut down when all references are released (including interna references -- Ken Halter - MS-MVP-VB - http://www.vbsight.co Please keep it in the groups. "rshawn" <anonymous@discussions.microsoft.com> wrote in messag news:87935380-AEBA-4402-AAD7-B9B28CA70F4C@microsoft.com.. > I have an ActiveX Exe component that has a singleuse object > One of the reference to this object is created in the client application, the othe reference is created at the bas module in the Exe_server itself > For some reason I keep getting the "Type Mismatch" error when creating a reference t this singleuse objcet from the client app > It is not even a consistent error because sometimes the client app is able to create th reference without any errors. This is the case when I am using both the client an Exe_server in the debug mode (i.e separate instances of VB IDE >> However when I try to use the compiled version of the client with the compile executalble of the Active Exe_server, the error is consistent. The client is never able t create a reference to the singleuse object. I get the same "Type Mismatch" error all th time >> The shared reference to the singleuse object is exposed by pointing all the reference t a global variable declared in the bas mod of the Exe_Server >> Has anyone come across this problem? Is this a bug in VB that I am unaware of >> thank > r |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.