Re: Large varchar columns with SQL server

I have looked at those articles, but I'm concerned with large varchar
fields (not text fields) and the situation where no error is returned
(but no data is returned when using rs(fieldname) syntax). If anyone
has any experience with this problem and which situations it appears
and does not appear in, I'd appreciate hearing about it.

Brian

Stephen Howe wrote:
I'm trying to track down some bugs that I read about at
http://www.aspfaq.com/show.asp?id=2188. I'm connecting to a SQL
database in ASP. Does anyone know specifically what configurations
(e.g., what versions of MDAC, what types of connections, etc.) cause
these bugs to appear? (I'm most concerned about the bugs that cause no
error to display but return no data from the field.)

No. If there was more information from Microsoft on this, don't you think
there would be now a published KB article?
The fact that 2 MVPs can't lay their hands on this information means it
probably does not exist.
Did you read the KB articles they pointed to:
http://support.microsoft.com/default.aspx/kb/200124
http://support.microsoft.com/default.aspx/kb/175239
???

I can also add that since ADO 2.6, if you do get DB_E_ERRORSOCCURRED on
,modifying a field, you check Field.Status to get feedback on what went
wrong.

For myself, I can immediately mention flaws
(i) deficencies in ADO documentation
(ii) under-documentation of IADORecordBinding to the point where some code
"fails".
(iii) some of the Microsoft VC++ examples are "exception-unsafe" despite the
fact that Microsoft has some decent smartptr's for ADO.
(iv) over complicated VC++ example of ADO event handling. There is more code
present than is necessary to demonstrate event handling.

All of this shows how "unfinished" ADO is, so it is unrealistic to imagine
that there will be large articles documenting every last nuance of your
problem.

Stephen Howe

.

Relevant Pages

  • Re: I need advice on disconnected clients
    ... ADO.NET is much lighter than ADO in many respects. ... criteria that need to be enforced on the client. ... any object in the database. ... > Read/Write .NET articles ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Possible DAO and ADO conflicts
    ... I'll take a look at those articles. ... It is on whether to convert DAO to ADO ... >> I have a legacy application which only has DAO references. ...
    (microsoft.public.vb.database)
  • Re: Large varchar columns with SQL server
    ... I'm connecting to a SQL ... Did you read the KB articles they pointed to: ... I can also add that since ADO 2.6, if you do get DB_E_ERRORSOCCURRED on ... present than is necessary to demonstrate event handling. ...
    (microsoft.public.data.ado)
  • Re: Possible DAO and ADO conflicts
    ... Here's a couple more articles that might help you: ... It is on whether to convert DAO to ADO ... > I have a legacy application which only has DAO references. ...
    (microsoft.public.vb.database)