Dean Cleaver wrote: > Means I have to have 2 different database access methods, although I > guess that's not so bad now - have to get out of the COM mindset and > think assemblies...
If you use the OleDb* family of classes and limit yourself to the lowest common denominator, it's just one set of code (controlled by an external connection string). That's not always possible (or even feasable), so yeah, drop in data layers would be the next best thing. The primary problem you fight with XML is that it's not a database, no matter how much its advocates wish is were. ;) XPath is nice, but if you have lots of data, it's just not smart to load up a DOM just to search. Even Access is going to beat that kind of thing black-and-blue. Good luck. :) Brad -- Read my web log at http://www.quality.nu/dotnetguy/ You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
