DCOM and the IStrings interface with OLEnterprise
Charles Little
across a serious problem. I need to pass lists of parameters, so am storing
them in a string list, using GetOLEStrings to get an IStrings interface to
it, then passing it to the server. The problem is, it works in a
non-distributed environment, but fails even in the simplest case
distributed. I have tried a few different approches, including defining the
parameter as IStrings, defining the Parameter as IUnknown, hard casting is
as IDispatch, and soft casting it to IStrings, and Defining the paramter as
a variant, soft casting it as IDispatch, and hard casting it to IStrings,
but even though all of them work non-distributed, they all totally fail
distributed.
Thoughts?
_________________________________________________
Charles Little
Software Engineer
e-mail: charles...@zcsterling.com, cli...@infinite-visions.com;
voice: 770.226.1915
_________________________________________________
Programming is an art form that fights back
Profanity is the one language all programmers understand
Sleep is for people that can't program
In /dev/null no one can hear you scream
Dan Miser (TeamB)
11/20/98. Let me know if that doesn't work.
--
Dan Miser
http://www.execpc.com/~dmiser
Dan Miser (TeamB)
deployed and registered on both the server and the client. That should
hopefully clear it up.
Charles Little
>11/20/98. Let me know if that doesn't work.
"Interface not Supported" distributed. It did work non-destributed,
however, just like all of the other cases.
__________________________________________________
Charles Little
Software Engineer
e-mail: charles...@zcsterling.com, cli...@infinite-visions.com; voice:
770.226.1915
Charles Little
Dan Miser (TeamB) wrote...
>Make sure STDVCL40.DLL (for Delphi 4) or STDVCL32.DLL (for Delphi 3) is
>deployed and registered on both the server and the client. That should
>hopefully clear it up.
The IStrings comes across as a variant, and the Exception is occurring on
the soft cast (as IStrings). If I separate the soft cast out, there is no
exception(the variable is not useable, however...)
If I do nothing to the IStrings when it comes across, I can use it directly
from the appserver, and it comes across fine, i.e. on the client:
var
idx: Integer;
begin
with RemoteServer1 do
begin
for idx := 0 to AppServer.MyStrings.Count -1 do
begin
Memo1.Lines.Add(AppServer.MyStrings[idx]);
end;
end;
end;
This works...I am now totally confused...
Dan Miser [TeamB]
That points to a configuration issue on your end. I would start by
looking through regedit for the string "stdvcl" and fix up any invalid
references.
It looks like you are using D3. Make sure the copy of STDVCL32.DLL you
have registered on both machines is the latest version of that DLL.
(I've got 8/5/97 3:01 am - 345,536 on my system). Also make sure you
only have one copy of the DLL on these systems.
--
Dan Miser
http://www.execpc.com/~dmiser
Please post MIDAS-related messages in inprise.public.midas
Charles Little
issues now, but i just wanted to make sure that your test scenario is being
done distributed, i.e. client on one machine, broker(if used) on another,
and server on another...
If it will help, I can send you my examples...just let me know.
Dan Miser [TeamB] wrote in message ...
Dan Miser [TeamB]
your registry contains the proper declarations for that instead of
STDVCL32.DLL. When using Delphi 4, you should use the
TDispatchConnection components, as opposed to TRemoteServer.
And to answer your question, yes, the test I performed was with the
client on one machine and the server on another.
Charles Little
Dan Miser [TeamB] wrote in message ...
>your registry contains the proper declarations for that instead of
>STDVCL32.DLL.
registered, also, I receive a "Library not registered" error.
>When using Delphi 4, you should use the
>TDispatchConnection components, as opposed to TRemoteServer.
>
Object Factory running with the server exported on the server.
Dan Miser [TeamB]
unregistering stdvcl32.dll and stdvcl40.dll. Then search through the
registry for any mention of stdvcl. Are any references left to stdvcl?
Lastly, register the stdvcl40.dll again (only) on both computers.
If this doesn't do it, let me know and I'll post my sample to my web
site. It will take a little while because I'll be pretty scarce here
for the next couple of weeks.
Lastly, just use DCOMConnection for now until this problem is solved to
remove extra layers.
Charles Little
>unregistering stdvcl32.dll and stdvcl40.dll. Then search through the
>registry for any mention of stdvcl. Are any references left to stdvcl?
>Lastly, register the stdvcl40.dll again (only) on both computers.
>
worked. So it seems to be a configuration problem, as you suspected.
Thanks for your help. I'll look into it from here...
Charles Little
Charles Little wrote in message <73uqsa$m0...@forums.borland.com>...
up. Once I did, the DCOMConnection worked fine. However, the OLEnterprise
connection gives an 'Interface not supported' error. I tried this on two
different clients with the same result. The project was the same as your
example.
Dan Miser [TeamB]
your only problem, then I would use the Text property of the TStrings
and pass it across as a Widestring.
Charles Little
limited to 255 characters. Is this true?
Dan Miser [TeamB] wrote in message ...
Dan Miser (TeamB)
Delphi 1 strings and those declared as shortstring). Otherwise, there is a
2GB limit. Take a look at the online help for "long string types" for more
information.
Charles Little wrote in message <74grnr$7s...@forums.borland.com>...
Charles Little
as an interface to the remote string list. This does not help me, but it
may help someone else...