I've got a program which works on a Windows XP Pro machine,
but fails on a Windows 2000 Server machine. This matters
for me, since I'd like to be able to develop on a different
computer than the production machine.

As far as I can tell, the .Net and ODBC stuff is identical
(or as identical as I can make it) on both systems.

Using Microsoft.Data.Odbc, the OdbcDataReader seems to
cough and die when it reaches a field which is empty. On
the XP machine, the reader acts fine, spitting out exactly
nothing for those fields which are empty. On the 2000
machine, output stops at the first empty field with the
following message:

"NO_DATA - no error information availale"

Can anyone suggest a direction to look in to fix this?

As an aside, I found a knowledge base article for something
similar (but not a solution):
http://support.microsoft.com/default...b;en-us;319243

On Thu, 20 Nov 2003 12:52:06 -0800, "Mike Davison"
<anonymous (AT) discussions (DOT) microsoft.com> wrote:


Dear Mike

Have you tried installing the patch on the target Windows 2000 server
following the link...

http://download.microsoft.com/downlo...MDAC27_x86.exe

(it's from the knowledge base article you found).

This fix worked for us.

Alternatively you could use framework version 1.1 and then you have no
need for Microsoft.Data.Odbc (it's replaced by System.Data.Odbc).

Hope this helps

Regards

Neil Allen

Thanks for the reply.

Yes, I attempted to apply the patch, but the system I was
installing it on doesn't have SQL Server, so the install
halted (rightly so).

I'll use System.Data.Odbc and hopefully avoid the issue
entirely.

Thank you again,
Mike Davison