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

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

Post by Pete Turnbu » Tue, 14 May 2002 15:55:51



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

 
 
 

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

Post by Carl Prothma » Tue, 14 May 2002 16:21:30



> 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

 
 
 

1. 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

2. How can I make a copy of Paradox table during runtime

3. Transaction Logs

4. mdac 2.1 to mdac 2.6

5. ISQL from Windows/DOS

6. big issue between MDAC 2.6 and MDAC 2.5

7. Update statistics and sp_recompile

8. Mdac 2.6 sp1 on clients using vb6 mdac 2.5 - hey Serge Shakhov

9. Differences between MDAC 2.1 & 2.6

10. HELP: MDAC 2.1 and MDAC 2.5