Thank you for the feedback. These requests have been an ongoing discussion with the team, both internally and externally. Especially with our continuously increased focus on establishing a stronger Access-SQL experience, we do plan to have some requests on this work looked further into within the next year. We will keep you posted with specific feature designs in scope as well as timelines. In the interim, you can continue checking our public roadmap for feature updates.Sascha Trowitzsch supported this idea ·
An error occurred while saving the commentSascha Trowitzsch commented
Indeed ODBCDirect had been a highly underestimated feature. IMO that's due the fact that formerly SQL servers were rather expensive and that developers had to much respect too the complexity of SQL servers. So only a few complained when it deprecated.
Times changed and now we have a bunch of free DBMS engines. Not only MSSQL but also Oracle Express, DB2 Express, MySQL/MariaDB, Postgres, Firebird,... and maybe SQLite, some of them being rising stars if you look at db-engines.com. I personally use MariaDB for the backend as it also runs on LINUX.
ADODB is no solution because many DBMS don't offer appropriate OLEDB Providers (unstable, unperformant) and the MS-ODBC-Provider is a senseless bottleneck.
MS took off the Access Projects and recommended ODBC as an interface while making to handle this more difficult in removing ODBCDirect at the same time. I never understood that.
So I would vote for bringing ODBCDirect back in a first step and further adjust that interface in ACEDAO to a more modern state.