Problem binding dispatch interface when client runs under WinNT

Thread View: borland.public.cppbuilder.database.multi-tier

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by John Graham Sat, 26 May 2001 11:58

#642

Author: John Graham
Date: Sat, 26 May 2001 11:58

44 lines
2381 bytes

Help!

I recently ported a BCB4 nTier app., developed on a PC running Win NT,
to BCB5 running under Win 2000.  Both the client and app. server
applications run fine on the Win 2000 PC.  However, when I run the
client on an NT PC, I get an error attempting to bind the dispatch
interface.

The client uses the Bind() method of the TAutoDriver class this way:

  SMSrvrDisp = new ISysManSrvrRDMDisp();

  SMSrvrDisp->Bind(WideString(SysManScktConnect->ServerName));

  if ( !SMSrvrDisp->IsBound() )
   {
     Application->MessageBox("Can't Bind Dispatch Interface -
Aborting!", "Rats!", MB_ICONEXCLAMATION);

   Application->Terminate();
  }

If I comment the error trap out, the BCB5 client runs fine on the NT
machine.  It connects to the app. server on the Win 2000 PC and can
write to and read from an MS SQL Server 7 database so long as I don't
try to call an app. server method using the dispatch interface.  Looks
like something is wrong with the way I'm trying to bind the interface.

Conversely, if I employ the Bind() syntax used in the BCB4 version of
the client,

  SMSrvrDisp->Bind(LPDISPATCH(SysManScktConnect->AppServer));,

It errors when both client and server are running on the 2000 machine as
well.

The BCB4 version of this app. developed on the NT PC allows the client
to run under any Windows OS ( 95 and above ) with the app. server
running on any of our NT servers.

What am I missing?

Regards,
John

Re: Problem binding dispatch interface when client runs under WinNT

#643

Author: John Graham
Date: Sat, 26 May 2001 16:16

52 lines
2837 bytes

Me again.  I forgot to mention that I have purchased two MIDAS server
licenses for BCB5.  What I got was two pieces of paper with serial number
and authorization key labels on them, but no instructions as to what to do
with the numbers.  I wonder if this is part of the problem?
John

John Graham wrote:

> Help!
>
> I recently ported a BCB4 nTier app., developed on a PC running Win NT,
> to BCB5 running under Win 2000.  Both the client and app. server
> applications run fine on the Win 2000 PC.  However, when I run the
> client on an NT PC, I get an error attempting to bind the dispatch
> interface.
>
> The client uses the Bind() method of the TAutoDriver class this way:
>
>   SMSrvrDisp = new ISysManSrvrRDMDisp();
>
>   SMSrvrDisp->Bind(WideString(SysManScktConnect->ServerName));
>
>   if ( !SMSrvrDisp->IsBound() )
>    {
>      Application->MessageBox("Can't Bind Dispatch Interface -
> Aborting!", "Rats!", MB_ICONEXCLAMATION);
>
>    Application->Terminate();
>   }
>
> If I comment the error trap out, the BCB5 client runs fine on the NT
> machine.  It connects to the app. server on the Win 2000 PC and can
> write to and read from an MS SQL Server 7 database so long as I don't
> try to call an app. server method using the dispatch interface.  Looks
> like something is wrong with the way I'm trying to bind the interface.
>
> Conversely, if I employ the Bind() syntax used in the BCB4 version of
> the client,
>
>   SMSrvrDisp->Bind(LPDISPATCH(SysManScktConnect->AppServer));,
>
> It errors when both client and server are running on the 2000 machine as
> well.
>
> The BCB4 version of this app. developed on the NT PC allows the client
> to run under any Windows OS ( 95 and above ) with the app. server
> running on any of our NT servers.
>
> What am I missing?
>
> Regards,
> John

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads