I have a large MSAccess Production/Sales application which has been evolving over the last 15 years. I've decided to bite the bullet and rewrite it in C#. There are a number of factors to consider, but the most important is to decided how to access the SqlServer data. I've been very happy using ADODB, and I was pleased to find that I can continue to use it in C#. However the modern way is to use SQLConnection. I don't mind the learning curve so long as it does what I need. I was reading last night that as a default, only one recordset can be opened on a connection, and that this can be overridden to allow more. There are numerous places in my application where there are multiple recordsets open. So I certainly need this facility.
So I was wondering what you guys in here think? SQLConnection is supposedly more efficient, but actually I have no issues with the efficiency of ADODB. Should I stick with what I know and trust? Or should I move with the times move over to SQLConnection?