Not able to open MSDataShape connection
From: Live_Love_Laugh (OnlineSubscribe_at_yahoo.com)
Date: 04/26/04
- Next message: Ross B.: "[ 10048 - Internal App ]"
- Previous message: AA2e72E: "RE: Difference between adDate and adDBDate?"
- Next in thread: Live_Love_Laugh: "Re: Not able to open MSDataShape connection"
- Reply: Live_Love_Laugh: "Re: Not able to open MSDataShape connection"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 26 Apr 2004 10:34:53 -0400
I am trying to test for compatiblity by moving SQL Server database from SQL
7.0 to SQL 2000 and at the same time, the server is being upgraded from
Windows 2000 to Windows 2003 server.
Our DNA based application which was working fine under SQL 7.0 on Windows
2000 server. With SQL2K and Windows 2003 it is not working as expected.
My application uses transaction based COM components hosted under COM+. The
application is not able to connect to the OLEDB MSDataShape provider. The
application hangs when it executes the ADO Connection's Open method with
MsDataShape connection string.
The COM+ environment is on a different machine than the Database Server. We
are using VB6 components and ADO 2.6 SP2 to connect to the database.
Are there any issues with datashape on SQL Server 2000 if components are
running under COM+ as a transaction?
Thanks,
Live_Love_Laugh
- Next message: Ross B.: "[ 10048 - Internal App ]"
- Previous message: AA2e72E: "RE: Difference between adDate and adDBDate?"
- Next in thread: Live_Love_Laugh: "Re: Not able to open MSDataShape connection"
- Reply: Live_Love_Laugh: "Re: Not able to open MSDataShape connection"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|