title: ADO vs ADO.NET: when to use each?
body: <p>I realize this is somewhat of an opinion question but I'd like to hear some people's insights. </p>
  
  <p>I'm working in VBA and VB.NET and currently use ADO to INSERT, UPDATE, and SELECT records in a PostgreSQL database using Excel as the user interface. ADO works great but it seems MS pushes ADO.NET as being the better tool, but my problem with it is that I'd have to create almost the entire PostgreSQL database as an in-memory dataset which I believe is unneeded because then I'm just copying entirely what's already on the server plus it's a lot to hold in memory.</p>
  
  <p>That said, what is everyone's thoughts on ADO vs ADO.NET given the situation of having to recreate nearly the entire database in memory for ADO.NET to do what ADO currently does? Is ADO still a relevant solution in some cases nowadays? Is there another alternative tech that someone would recommend?</p>