.NET Framework and ADO

[=?Utf-8?B?SkQ=?=]

Recently I had several users run an app, written in VB6 using ADO 2.6 (their
requirement, not mine). One particular SQL statement gave problems to one of
the users. The statement was a single string executed via command object
such as:
USE mydatabase
SELECT name FROM mytable

The string included a vbCrLf pair to separate the lines.

The one person who did not have .NET Framework 2.0 installed got back a
recordset whose state was adStateClosed. The
cmd.ActiveConnection.Errors.Count was zero.

That leads to my question: Does installing the .NET Framework 2.0 update
any of the ADO COM objects, or some dependency that would cause this change
in behavior? None of the folks with 2.0 installed have this problem. The
same SQL string executes without a problem. All users used the same
binaries, the same database on the same server, and all have the same network
and local priviledges.

Thanks in advance.
--
JD
Developer