ADO and ADO.NET are two different animals.
The recordset of ADO exists no more.
If you are bringing data into your application, the only way you could write code the way you describe is by returning all of your data in arrays or assigning all individual fields in your class module (and that would be a pain in the butt - just as easy to move to ado.net now). So only that module references ADO. If you are just calling stored procedures to execute inserts, updates, deletions - then what you are proposing would be easier - but that does not seem like a real life scenario.