MDAC 2.8 vs MDAC 2.7
From: Gianluca (Gianluca_at_discussions.microsoft.com)
Date: 10/28/04
- Next message: baskar: "AddNew Fails when too many fields are added"
- Previous message: cityofgp: "Re: Access VBA update recordset error"
- Next in thread: Jiho Han: "Re: MDAC 2.8 vs MDAC 2.7"
- Reply: Jiho Han: "Re: MDAC 2.8 vs MDAC 2.7"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 28 Oct 2004 12:55:02 -0700
I have written several vb6 applications with MDAC 2.7 SP1 Refresh.
This application connects to a SQL Server 2000 SP3a on Windows 20003 Server.
I run this application on a WXP Pro client.
I have a DSN defined to connect to SQLServer via ODBC
All works ok with this code:
Dim cn1 as new adodb.connection
Dim rst as ADODB.Recordset
Dim lngNumber as long
cn1.ConnectionTimeout = 60
cn1.CursorLocation = adUseClient
cn1.Open "DSN=" & sName, sUser, sPwd
rst.Open "SELECT ID FROM TABLE", cn1, adOpenKeyset, adLockOptimistic
lngNumber = rst.Recordcount
' Note that lngNumber = 3567
if lngNumber=0 then MsgBox "Error"
....
If i put the application on Windows 2003 server i get:
' The same table with 3567 records return 0
if lngNumber=0 then MsgBox "Error"
and the Box "Error" appears!!!!!
I changed to OleDB and It works but the problem is:
when all my server will be Win 2003 I will have lots of
program with problems !!!!!!
How can i continue in using DSN with ODBC with Windows 2003 server ?
My customers are not enthusiastic to pay me to
change all programs !
Help me please
Thank you
- Next message: baskar: "AddNew Fails when too many fields are added"
- Previous message: cityofgp: "Re: Access VBA update recordset error"
- Next in thread: Jiho Han: "Re: MDAC 2.8 vs MDAC 2.7"
- Reply: Jiho Han: "Re: MDAC 2.8 vs MDAC 2.7"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
