BorlandTalk.com

George Wynne · Guest

D7

I'm using SQL Server, and I have triggers and stored procedures that
reference the user with the reserved word "system_user". When I
connect to my app server using sockets, SQL Server identifies
"system_user" as the user that is logged into the server machine.
That's no good - I need it to get the user on the client. It this
possible using sockets?

I suspect that I need to use DCOM to do this. It this right?

Anyway, I been very frustrated in my attempts to connect to another
machine using DCOM so far. Are these DCOM connection problems the main
disadvantages of DCOM, or are there other problems? I've gone through
http://www.distribucon.com/dcom95.html, but it does not suggest what
may be wrong when the client app freezes when trying to connect.
Here's my original DCOM connection post from a few weeks ago. Any
help?

"I created an application server with a remote data module and ran it
to register it. Then I created a client app with a TDCOMConnection,
left ComputerName blank, set ServerName, and set Connection := true.
So far, so good.

Then I moved the app server to a server machine and ran it. On my
client app, I set ComputerName to the server machine name. Then I
clicked on ServerName, and the list of possible servers is the list
that is available on my machine, not the server machine. Why is that?
And then I try to set Connected := true, and that completely locks up
Delphi and I have to Ctrl-Alt-Del to kill Delphi. Not good.

I've also tried setting Connected := true at run-time, but that
similarly locks up my client app.

What am I doing wrong?"

Thanks,
George