Com With multiple reference conflict
-
Hi All, I am using one com dll and have multiple clients on the same machine which are creating pointers for same interface, so is there can be any conflict. Example: SomeComComponentLib::IsomeInterface objInterfaceptr; .....create instance Now all the client applications are using objInterfaceptr in same way...Please provide me some suggestion to avoid conflict.
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
-
Hi All, I am using one com dll and have multiple clients on the same machine which are creating pointers for same interface, so is there can be any conflict. Example: SomeComComponentLib::IsomeInterface objInterfaceptr; .....create instance Now all the client applications are using objInterfaceptr in same way...Please provide me some suggestion to avoid conflict.
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
What conflict? :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles] -
What conflict? :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles]Actually i want to ask that can it cause any coflict... in my situation: Some times i am not able to use the method of the interface object. like application doesnt acknowledge the object and returns without performing the task.
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
-
Actually i want to ask that can it cause any coflict... in my situation: Some times i am not able to use the method of the interface object. like application doesnt acknowledge the object and returns without performing the task.
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
Ash_VCPP wrote:
Actually i want to ask that can it cause any coflict...
I suppose not (but, without code, is a blind guess).
Ash_VCPP wrote:
Some times i am not able to use the method of the interface object. like application doesnt acknowledge the object and returns without performing the task.
What do you mean with: "application doesn't acknowledge the object?". Do you get errors? :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles] -
Ash_VCPP wrote:
Actually i want to ask that can it cause any coflict...
I suppose not (but, without code, is a blind guess).
Ash_VCPP wrote:
Some times i am not able to use the method of the interface object. like application doesnt acknowledge the object and returns without performing the task.
What do you mean with: "application doesn't acknowledge the object?". Do you get errors? :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles]Ok let me explain you the problem in detail... i am using msscript.ocx to get script support, now i am using one com dll and using its interface and adding interface object in script object, now script is using these object without initializing it, now i have same application running multiple times on same machine repeating the process, but some times vbscript doesnt acknoledge the interface objects. Example:
m_ScriptObj.AddObject("DataIn", DataIn, false);
m_ScriptObj.AddObject("DataOut", DataOut, false);
m_ScriptObj.AddObject("Parser", Parser, false);
m_ScriptObj.AddObject("Setting", Setting, false);now suppose i am using DataIn object inside my vbscript, and here comes the Inconsistent behaviour.
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
-
Ok let me explain you the problem in detail... i am using msscript.ocx to get script support, now i am using one com dll and using its interface and adding interface object in script object, now script is using these object without initializing it, now i have same application running multiple times on same machine repeating the process, but some times vbscript doesnt acknoledge the interface objects. Example:
m_ScriptObj.AddObject("DataIn", DataIn, false);
m_ScriptObj.AddObject("DataOut", DataOut, false);
m_ScriptObj.AddObject("Parser", Parser, false);
m_ScriptObj.AddObject("Setting", Setting, false);now suppose i am using DataIn object inside my vbscript, and here comes the Inconsistent behaviour.
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
Unfortunately it looks like there is no documentation about the script control (or I am not able to find it...). I have used it in the past, but I never needed the
AddObjectmethod. :(If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles]