I found a mdac 2.8 bug.
I am using Windows 2000 SP3, VB6 SP5 and SQL Server 2000 SP3.
I select a table with a field of money type. If the field value is a large
negative value
( ex. -348000000000.1234), the select result will be
wrong((-122820018631.5986).
Can anyone verify whether this is a mdac 2.8 bug?
Re: large varchar columns in SQL server ... different than the bug we were talking about. ... I didn't know that truncation was part of the bug. ... The other confusing thing is that later versions of mdac appear in ... This email account is my spam trap so ... (microsoft.public.inetserver.asp.db)
Re: large varchar columns in SQL server ... different than the bug we were talking about. ... I didn't know that truncation was part of the bug. ... The other confusing thing is that later versions of mdac appear in ... This email account is my spam trap so I ... (microsoft.public.inetserver.asp.db)
Re: large varchar columns in SQL server ... So with SQLOLEDB the problem won't occur regardless of MDAC version? ... different than the bug we were talking about. ...Microsoft MVP - ASP/ASP.NET ... This email account is my spam trap so ... (microsoft.public.inetserver.asp.db)
Re: large varchar columns in SQL server ... different than the bug we were talking about. ... I didn't know that truncation was part of the bug. ... it does not occur when using Mdac... I suspect that behavior was built into the earlier driver to ... (microsoft.public.inetserver.asp.db)
Re: mdac 2.8 bug? ... > I found a mdac 2.8 bug.... Verify that the data is actually OK coming from your sql server to start ... I have seen problems with vb6 where a jscript passes a ... (microsoft.public.vb.database.ado)
