Database Wrapper?

[Answer]

I a currently coding a project that uses several, well actually many databases. What i was thinkin of doing was creating a class for each db then coding in certain functions that are not included in ADO that i want. Such as a speciallized sorting and adding records except in a more user freindly way specific to each db.

 

My question is, should i jsut make a property that exposes teh recordset for each class. Or should i make a base class that is inherited that would include a methods to do basic database stuff like moving, filtering etc.. This way the clients are not exposed to the recordset at all. Then make propertys for each db that would represent each field.value in the db i wanted to make available.

 

Is there any downside to doing this that i cant see? I can see a ton of advantages. All of these classes will be put into a .dll for use in a larger program.

 

this is a vb.net project also, if that makes any difference.

[Robby]

Your second idea sounds good.

 

btw, when you say recordset, do you mean resultset?

[Answer]

No Recordset, ADO.NET offers piss poor performance for ISAM databases such as dbase. At least that is my findings. I have spent days trying to get ADO.NET to meet ADO's performance.

 

ADO.NET takes like 3 minutes to where ADO takes .4 secs