The current database driver design has a flaw, that the control which offers the user to specify connection information is not part of the driver, but part of the main application (LLBLGenPro.exe). This means that if I don't add the control, the driver can't be written. I first have to make that change, to move the control from the main app into the driver assemblies. I'll do this when more gui enhancements are implemented, which is right after the adapter finalization.
After that I've planned to add ms access support because that's requested a lot and mysql, if I can find a way to install the latest mysql version on my testboxes and can work with it (I never worked with mysql). If it's too cumbersome I'll drop it and leave it to others to write a mysql driver (you then can because the control is inside the driver by then). DB2 still doesn't have a .NET provider, despite IBM's claims, so right after that I'll look into Firebird/interbase. Adapter took more time than anticipated, and I don't think it will be january when I can start working on firebird interbase support.
The comming months are very busy, a lot of functionality has to be implemented, like designer support for inheritance, mapping classes onto tables, adding custom properties etc. It's not yet decided what is more important, however I lean towards implementing major gui enhancements first and other database support later, but again that is not yet decided. Personally I'd like to support DB2 and Firebird first and ms access later, (I don't see ms access as a database even, it's nice for rad apps but not for database usage), but people ask for it a lot. I do my best to get firebird/interbase support as soon as possible.
