Re: large varchar columns in SQL server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

The code did use SELECT * and did not write the values to variables
before outputting. Is there a version of MDAC that these bugs are
completely gone from, regardless of how I am connecting to the
database, querying the database, or storing the values? This page was
produced around 4/2005.

Brian

Aaron Bertrand [SQL Server MVP] wrote:
I am trying to diagnose whether this problem affected some web
applications that I had written (and were run) some time ago, so I
can't be sure what version of MDAC they were run under. If I see that
access to the large varchar (or memo) fields worked at least some of
the time, can I be sure that this error didn't afflict my app? (For
example, I had users' data stored in a SQL server database that was
later retrieved via an ASP script that wrote out the values of the
fields (for each record) to a web page; the original SQL server
database is gone but we kept the resulting web page. I want to make
sure that no data is missing from this web page.)

As Bob suggests, it's going to be really hard to tell. Do you still have
the ASP code that retrieved the data at least? If so, check to make sure
that the code (a) did not use select *, (b) named memo columns last, and (c)
stuffed the value into a variable before writing it out. If some of those
things weren't done, then if MDAC was old and bad enough (do you have a
rough timeframe when the page was produced?), you may have had empty
strings. Bob also mentioned that the problem was intermittent, so it could
have gone one way or the other, and I think it would be impossible to know
for sure, even if you can collect all of the data above, unless you can find
the data source from somewhere and compare.

A

.

Relevant Pages

  • Re: How to represent category, subcategory, product
    ... I waited days with no reply on a SQL Server ... Thanks Gene, Lennart, Neo, Bob for your suggestions, some very helpful ... Neo, your suggestion is intriguing, I'll be looking into it. ... haven't found any database counterparts of the libraries of algorithms ...
    (comp.databases.theory)
  • RE: SQL server Login connection failed sqlstate 28000 sql server e
    ... mdac 2.8 - ran the mdac checker and everything is fine ... and reconnect to the sql server using odbc - dsn connection. ... Now when we make mods to the database, reconnect, then we get that error. ... please download Component Checker from the link below to make sure ...
    (microsoft.public.sqlserver.odbc)
  • Re: large varchar columns in SQL server
    ... I had users' data stored in a SQL server database that was ... database is gone but we kept the resulting web page. ... Depending on the version of your MDAC driver, ...
    (microsoft.public.inetserver.asp.db)
  • error 3021 no current record, only sometimes
    ... I have an Access 97 database front end (with some lookup tables there ... too) which also has a MS SQL Server 2000 back end, ... getting ODBC errors when trying to open ... way and the same version of MDAC. ...
    (comp.databases.ms-access)
  • Re: 64 bit MDAC needed
    ... MDB uses Jet Engine, which is 32 bit, and will not have 64 bit version, for sure. ... You may consider to upgrade your *.mdb database to *.accdb, then use MS Access database engine. ... If you can use MySQL, I do not see why you cannot use SQL Server Express. ... I'm in desperate need for 64bit MDAC components. ...
    (microsoft.public.dotnet.general)