Hi All,
This didn't get a response in the VB forum, so am trying it here.
I've got an issue with SQL Server 2000.
I have VB6 components using Objectcontext (transactions) running on machine A. When I try and get them to connect to my SQL database on machine B, the connection looks like it's made, but it hangs the application, and in SQL I can see the status of the connection is "Awaiting Command". It never timesout.
When I try to connect my components to a database running on machine A (same as components), I get connected fine, and can run the sql from my components.
Getting pretty frustrated. In VB6, I can change the transactional settings of my components. When I remove any transactional settings, I can connect ok to sql database on Machine B.
Is there some setting in SQL Server which restrict how transactional connections can be made? Has anyone come across a similar problem? Thanks
This didn't get a response in the VB forum, so am trying it here.
I've got an issue with SQL Server 2000.
I have VB6 components using Objectcontext (transactions) running on machine A. When I try and get them to connect to my SQL database on machine B, the connection looks like it's made, but it hangs the application, and in SQL I can see the status of the connection is "Awaiting Command". It never timesout.
When I try to connect my components to a database running on machine A (same as components), I get connected fine, and can run the sql from my components.
Getting pretty frustrated. In VB6, I can change the transactional settings of my components. When I remove any transactional settings, I can connect ok to sql database on Machine B.
Is there some setting in SQL Server which restrict how transactional connections can be made? Has anyone come across a similar problem? Thanks
