Originally posted by Dilenger4

Why would it be better to avoid ADO? Im just curious as to why you said that.
I'm just repeating something a Microsoft guy said at a recent seminar.

As I understand it (and I'm still wrestling with .net), you can still do most of the traditional VB stuff with .net, such as calling API's directly, usding ADO etc. but that this is mainly for backward compatability.

A 'pure' .net program does EVERYTHING through the .net framework. An 'impure' one does not.

This has certain implications. A 'pure' app can be installed just with xcopy (assuming the framework is installed on the target machine - which it will always be in future, since it will be installed along with the Windows operating system ). For a single file app, it is just a straight file copy. No DLLs, registration etc.

A 'pure' app will run unchaged on any operating system that has the framework installed - which in future may be ALL operating systems, if MS have their way.

An 'impure' app wil not enjoy these advantages.

At least that's what they told us.