🚀 go-pugleaf

It's me again with some additional data.

The Midas\Adhoc example provided with BCB5 doesn't work either.  That is, it
works as long as I run both the client and app. server on the same machine, but
when the app. server is deployed to my NT 4x workstation, no go.  This time I
followed the instructions to the letter for deployment contained in the
paperwork I got with my licenses using InstallShield.

I've been unable to call my app. server methods either through IDispatch or
IAppServer using Bind() as well as CoClassCreator::Create().

Someone out there MUST be using BCB 5 to develop nTier apps. with the app.
server running on a different machine.  I've run out of string and could sure
use some help.

Regards,
John


"John Graham ( SALTS Central )" wrote:

> Hi,
>
> Can anyone tell me how to bind the dispatch interface of a MIDAS application
> server running on a remote server to my client application?
>
> The client and app server were developed on a PC running Win 2000 using BCB5
> Enterprise.
>
> I have developed the same app. using BCB4 and have no problem binding the
> dispatch interface and using the resultant object to access application
> server methods that I wrote.  Can't seem to make it work using BCB5 though.
> Both versions of this app. employ TSocketConnection objects with
> ScktSrvr.exe running on the remote machine.
>
> The BCB5 client will start the BCB5 app. server on the remote machine, but
> errors out when the attempt is made to bind the dispatch interface to the
> client.
>
> I have googled and newsgrouped myself to death and am not getting anywhere.
> Every example I've found so far uses both client and app. server running on
> the same machine.  That works, but that's not what I want to do, and that's
> not the purpose of this technology.  I want to be able to run my client app.
> from anywhere in the world.
>
> In case there's some doubt out there, I have two server licenses which make
> it legal for me to install the app. server on two different file servers.

To access a Dispatch interface of your remote compnent use the following
Lines


IMyComponent * aComponent;

    aComponent = LPDISPATCH(DComConnection1->ApPServer);
IMyComponentDisp MyDisp(aComponent);

    MyDisp.DoSomething();



"John Graham" <jgraham@salts.navy.mil> wrote in message
news:3B236E44.3E381203@salts.navy.mil...
> It's me again with some additional data.
>
> The Midas\Adhoc example provided with BCB5 doesn't work either.  That is,
it
> works as long as I run both the client and app. server on the same
machine, but
> when the app. server is deployed to my NT 4x workstation, no go.  This
time I
> followed the instructions to the letter for deployment contained in the
> paperwork I got with my licenses using InstallShield.
>
> I've been unable to call my app. server methods either through IDispatch
or
> IAppServer using Bind() as well as CoClassCreator::Create().
>
> Someone out there MUST be using BCB 5 to develop nTier apps. with the app.
> server running on a different machine.  I've run out of string and could
sure
> use some help.
>
> Regards,
> John
>
>
> "John Graham ( SALTS Central )" wrote:
>
> > Hi,
> >
> > Can anyone tell me how to bind the dispatch interface of a MIDAS
application
> > server running on a remote server to my client application?
> >
> > The client and app server were developed on a PC running Win 2000 using
BCB5
> > Enterprise.
> >
> > I have developed the same app. using BCB4 and have no problem binding
the
> > dispatch interface and using the resultant object to access application
> > server methods that I wrote.  Can't seem to make it work using BCB5
though.
> > Both versions of this app. employ TSocketConnection objects with
> > ScktSrvr.exe running on the remote machine.
> >
> > The BCB5 client will start the BCB5 app. server on the remote machine,
but
> > errors out when the attempt is made to bind the dispatch interface to
the
> > client.
> >
> > I have googled and newsgrouped myself to death and am not getting
anywhere.
> > Every example I've found so far uses both client and app. server running
on
> > the same machine.  That works, but that's not what I want to do, and
that's
> > not the purpose of this technology.  I want to be able to run my client
app.
> > from anywhere in the world.
> >
> > In case there's some doubt out there, I have two server licenses which
make
> > it legal for me to install the app. server on two different file
servers.
>