The main goal of the v11 release was to ensure coexistence with changes to the database structure outside of the DataFlex tools. In v10, we removed the need for a structure cache files (.TD files) by increasing the performance of accessing table structure information in system tables. In v11, we added relationship synchronizer that exports DataFlex relationship to SQL backends and also allows relationship created directly on the backend to be imported into the DataFlex environment by updating the .INT file.

In addition we have completely revamped our documentation, adding new chapters to help users navigate through issues such as blob handling, code optimization for better performance and deployment issues.

The top new features of our v11 drivers include:

• Full control over table casing on the SQL side: Our v11 drivers now offer customers full control to determine whether table names are upper, lower or mixed case. In the past, all table names were migrated to upper case. This feature works in Flex2SQL, restructuring and through the DB Builder, and customers have programmatic and INI file control over it.
• Save multiple logins: Now both the driver and Flex2SQL allow you to save the last five servers you connected to in the login dialogs. This is a handy feature for users who alternate between two servers, such as a test and deployment server.
• Relationship synchronization: This new wizard function allows users to migrate relationships from Dataflex to SQL and/or SQL to Dataflex. This tool is important, for example, when using the Visual Report Writer. Relationships on the SQL Server also strengthen data integrity if changes are made outside of the regular Dataflex commands (for example: embedded SQL or other tools.)
• The database server as the data structure repository: We’ve completely reworked the import of existing SQL tables. This new feature makes it easy for customers to do their modeling work using existing SQL tools and import all the changes (including all relationships) into Dataflex. This opens up a new choice for customers to manage their database schema. In the past, customers were mostly limited to the DB Builder, VDF Studio or Flex2SQL, now they can use the SQL as the master repository of schema information, and quickly synch it back into Dataflex.
• Documentation revamp: We are redoing our documentation to describe all the new features and will include chapters on the little known features in the driver. The examples in mertech.inc have also been improved.
• Easier to consolidate multiple tables into one: We have implemented a new feature that we call a ‘programmatic default value’. It allows you to specify that if a column is not touched, then the previously set programmatic value will be automatically stored in it. This feature can be used in conjunction with SQL find constraints to effectively consolidate multiple copies of the same table (in different data folders) into one table on the SQL side. Normally this is on a customer basis, so the setup would be:
  1. Customer picks which customer they work with – before their application would navigate to the folder that held this database. Today they set up the programmatic default value to hold and constraint based on the customer ID. Any operations done will then ensure that the customer ID is properly respected.
  2. Customer picks another customer and sets the programmatic default to the new customer id. The application keeps working as before, but with the new customer.
  The benefit of the programmatic default value is that there are NO code changes needed except at the point where the current customer (or some other separating concept) is set and tables are opened.

• Complete support for native data types The v11 driver extends the support for native data types introduced in newer version of the various DBMS server. Beginning with our v10 drivers, we introduced support for all major datatypes specifically in MS SQL 2008, like the DATETIME2 type not supported in Visual DataFlex
• Improved script generation We’ve also extended SQL scripting to all parts of the migration, making it possible to script out the after loader steps and all other maintenance tasks that previously were only available directly through the Flex2SQL migration tool.
• Allows creating of RowID table in the migration tool We have extended our support for rowid tables further by allowing users to create rowid tables programmatically, as well as restructure existing recnum tables into rowid tables. We have included checkers to that can be used by customers to ensure that all inverse key columns have the correct values (for example if they are using non-Dataflex tools or ESQL to update affected columns).

  Our version 11 driver also allows you to save the SQL script that would be submitted to a server on restructuring. This makes it possible to generate new INT files as well as the SQL script that can then be deployed to a live server, for easier database updates.

  Another key change with the version 11 driver is that Mertech.inc has been revamped. This has significantly increased the speed of the embedded SQL and binding into variables. The size of compiled executables will also go down when using the new mertech.inc.

  We look forward to continuing to improve our products and welcome our customers feedback on our new v11 features or any other Mertech drivers you are using.