by Wayne Cressma » Thu, 09 May 2002 03:03:24
Regards,
Wayne C.
by Carl Huber [M » Fri, 10 May 2002 10:55:38
Release Manifest for MDAC 2.5 RTM (2.50.4403.12)
http://www.microsoft.com/data/MDAC25info/MDAC25rtmmanifest.htm
Release Manifest for MDAC 2.5 SP1 (2.51.5303.5)
http://www.microsoft.com/data/MDAC25info/MDAC25SP1Manifest.htm
Release Manifest for MDAC 2.5 SP2 (2.52.6019.2)
http://www.microsoft.com/data/MDAC25info/MDAC25SP2Manifest.htm
Regards,
Carl Huber, MCSD
Microsoft Developer Support/Visual Basic WebData
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! -> http://www.microsoft.com/security
by Wayne Cressma » Mon, 13 May 2002 09:55:52
Quote:> Hi Wayne,
> Here is a link to the release manifests for MDAC versions 2.5 RTM, 2.5
SP1,
> and 2.5 SP2. These documents contain specific information for each
> release, in addition to links to more information. All these and more
> found on www.microsoft.com/data.
> Release Manifest for MDAC 2.5 RTM (2.50.4403.12)
> http://www.microsoft.com/data/MDAC25info/MDAC25rtmmanifest.htm
> Release Manifest for MDAC 2.5 SP1 (2.51.5303.5)
> http://www.microsoft.com/data/MDAC25info/MDAC25SP1Manifest.htm
> Release Manifest for MDAC 2.5 SP2 (2.52.6019.2)
> http://www.microsoft.com/data/MDAC25info/MDAC25SP2Manifest.htm
> Regards,
> Carl Huber, MCSD
> Microsoft Developer Support/Visual Basic WebData
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Get Secure! -> http://www.microsoft.com/security
1. Problem when upgrading MDAC 2.1 to 2.5
This WebClass runs well when MDAC is in 2.1 (2.1.2 4202.3).
But when MDAC is upgraded to 2.5 (2.50 4403.12) on NT server, problem
happened; WebClass crashed with a "Out of Memory" showed up in the
beginning.
I debugged all day and found a consistent patten as shown in the
following explanation:
1) If there are more than 2 input query parameters and the
CursorLocation = adUseClient the WebClass will crash
The message on web is "out of memory" or "row handler must all be
released before new ones can be obtained".
2) if there are more than 2 input query parameters and the
CursorLocation = adUseServer then
RecordCount = -1 for all 12 combinations of 4 CursorType and 3
LockType .
3) If there are 2 parameters, when the CursorLocation = adUseClient,
RecordCount returns correct number for all 12 combinations of 4
CursorType and 3 LockType .
4) If there are 2 parameters, when the CursorLocation = adUseServer
then RecordCount = -1 for all 12 combinations of 4 CursorType and 3
LockType .
The coding is as following (I simplify the original coding to present
the relevant) :
<%
Set rs = New ADODB.Recordset
Set objConn = New ADODB.Connection
'rs.CursorType = adOpenForwardOnly
'rs.CursorType = adOpenKeyset
'rs.CursorType = adOpenDynamic
rs.CursorType = adOpenStatic
'rs.CursorLocation = adUseServer
rs.CursorLocation = adUseClient
'rs.LockType = adLockReadOnly
'rs.LockType = adLockPessimistic
rs.LockType = adLockOptimistic
objConn.Open "DRIVER={Sybase System
11};SRVR=TREE;DB=APPLE;UID=readonly;PWD=readonly;"
rs.Open "select red, green, yellow from APPLE" , objConn
Debug.Print rs.RecordCount
'rs.Close
'rs.ActiveConnection = Nothing
%>
Same problems happen on using MDAC 2.6 and even resuming to MDAC 2.1
which was running well before.
I can not resume the good running status, the program is no good for
any of the MDACs.
Since MDAC includes ODBC which defines the spec of API which different
ODBC driver uses to link to its DBMS,
will a change of MDAC from 2.1 to 2.5 have some impact on the Sybase
ODBC driver to make
the data fetching normally?
Does this mean that Sybase ODBC driver possibly have to be changed
when the MDAC is changed? if the
porting of data is not as smooth as before. In this case, there are
only 2 fields can be returned after the
MDAC is upgraded from 2.1 to 2.5; but originally there are more than 2
(it is 6 rows) returned without problem.
Do I miss anything? I do not understand Sybase ODBC driver that much
so please excuse me if I am wrong.
I appreciate any share of knowledge or experience of upgrading MDAC
2.1 to 2.5. Thanks in advance.
2. Problema con una stored procedure
3. Upgrade MDAC 2.1 to 2.5????
4. Help: how do you verify that your table goes into keep buffer
5. MDAC 2.1 (Jet 4.0) upgrade problems
6. Creating an index file for a Paradox 5.0 db file in Delphi 1.0
7. MDAC 2.1 upgrade geeks ASP's
8. Moving PDOXWIN to a network
9. HELP: MDAC 2.1 and MDAC 2.5
11. MDAC 2.6 on the Server and MDAC 2.1 on the Client - Big Problems
13. MDAC 2.0 Vs MDAC 2.1 - Compatibility Issues.