Dean Cleaver [mailto:[EMAIL PROTECTED]] wrote:
> That is a thought - use the OleDb rather than SQL, however > you pay a bit of a performance penalty - might be best to > code the SQL to be "cross-platform" and call into 2 different > data access classes instead - one coded for SQL, one for Access. But, there's another level of abstraction at the interface level. If you deal only with the abstract System.Data interfaces (IDbConnection, IDbCommand, et. al.) then you can factory methods to instantiate your types according to some configuration data. Then you're always (transparently) using the best implementation underneath. > Besides, you go the OleDb route only to get 99% of the way > there and find you can't get the last 1% to work, so have to > revert back - I hate that situation. Got a specific example? Maybe we can figure something out. HTH, Drew .NET MVP You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
