Visual Basic&database, MDAC 2.6 on the Server and MDAC 2.1 on the Client

MDAC 2.6 on the Server and MDAC 2.1 on the Client - Big Problems

Author	Message
Pete Turnbu #1 / 2	MDAC 2.6 on the Server and MDAC 2.1 on the Client - Big Problems We have recently developed an application that uses MTS 2.0 (4 external custom DLL's) on the server with MDAC 2.6 SP2 (accessing SQL Server 2000) which is accessed by client workstations that are running MDAC 2.1 SP2. Our application which is written in VB 6.0 SP5 and will not function correctly (it just doesn't create connections or return Recordsets or do anything requiring the MDAC, it just sits there). My Question is, does this type of environment actually work? and if so any suggestions and how to get it working. We don't want to upgrade to MDAC 2.6 on the client as this has the potential to break other applications that work with MDAC 2.1 and we require MDAC 2.6 on the server as we access SQL Server 2000 and return xml streams to the MTS components Any suggestions are welcome. Thanks Pete Turnbull
Fri, 29 Oct 2004 14:55:51 GMT

Carl Prothma #2 / 2	MDAC 2.6 on the Server and MDAC 2.1 on the Client - Big Problems Quote: > We have recently developed an application that uses MTS 2.0 (4 > external custom DLL's) on the server with MDAC 2.6 SP2 (accessing SQL > Server 2000) which is accessed by client workstations that are running > MDAC 2.1 SP2. Our application which is written in VB 6.0 SP5 and will > not function correctly (it just doesn't create connections or return > Recordsets or do anything requiring the MDAC, it just sits there). Pete, What do you mean by "it just sits there"? Also, how are the clients calling the COM+ components? DCOM? HTTP (via RDS Dataspace)? Is the COM+ package set to Server or Library? If Server, which Identity do you have set? Where is the connection being made? And what does your connection string look like? -- Thanks, Carl Prothman http://www.able-consulting.com
Fri, 29 Oct 2004 15:21:30 GMT

Page 1 of 1

[ 2 post ]