Overview
4D Products
4D Maintenance
Features
Getting Started with 4D
Resources
4D v11 SQL offers a new dimension in the connectivity of 4D applications. New means of incorporation and expansion are now available thanks to the rewritten engine and the SQL language. By simplifying and standardizing the data access procedures from third-party applications, we have massively improved the performance of our completely rewritten ODBC Driver, and we have removed the 4D Open filter that translated SQL requests for the old database engine.
4D Open therefore goes completely unused by 4D’s database engine. Specific applications using this protocol will have to be rewritten to be compatible with 4D v11 SQL.
Another common use of 4D Open is the 4D Open for 4D plug-in, allowing 4D Server to synchronize with other 4D applications, or to create a lightweight client for 4D Server. While we’re traditionally focused on backward compatibility for 4D applications, we had to in this case consider the strategic choices of maintaining compatibility with obsolete technology, versus working toward integrating new technologies.
We made this choice after consulting our principal users and partners by showing them our roadmap and the factors at stake. We eventually concluded to abandon the 4D Open for 4D plug-in in 4D v11 SQL.
Although 4D Open for 4D code cannot be migrated towards 4D v11 SQL, there are existing solutions for connectivity between 4D databases and users of the plug-in. Some are available immediately as SQL Pass-through using ODBC, Web services (again improved in v11.2), HTTP connections, or TCP/IP commands. It will soon be possible to use SQL Pass-Through mode between two 4D applications without installing additional drivers for optimal performance.
Release 3 of 4D v11 SQL will be an opportunity to complete new means of connection which while being faithful to the spirit of 4D Open for 4D, bringing ease of implementation (i.e. no specific language) and unequalled performance.
