Str8Dog wrote:
Borg, A simple solution to this would be a different architecture for the app. Maybe for version 8....
If you took a object oriented approach to data access it might simplify things a bit. Creating a data access object and using the methods of that object to retreve your recordsets for you would allow you to build your app on top of that object independant of the database it was using. That way everyone who wants to use MySQL can write a new data access object and plug it into the app. Seems like a pain in the ass, but in the end it makes the app more flexible..
To get a idea if what I mean, check out diggersolutions.com's Intranet Open Source. There is one file with all the sql calls. Very easy for someone to port that. |
I wouldn't say *simple*
, but yes it would be an ideal methedology.
ASP does allow classes however they're a bit limited. If you were going to create a data access layer using components, which would involve rearranging/rewriting quite a bit of the code, then I'd take the plunge and do it proprely in .NET
That said, I guess we could make a couple of include files with the DB-specific queries and do it that way..
Cheers,
Andrew