New Features in Version 2.0.0

oThis version contains a lot of changes and most of them (but not all) are covered here.

oImportant! The interface for the DbVersion table has been changed. The old syntax;

       Set Data_File_Field to File_Field DbVersion.DatabaseVersion has been depreciated.

If not changed you will get compile errors. The new interface consists of setting a couple of properties;

                   Set piDbVersionFileNumber to iSomeFreeFilelistNumber

                   Set piDbVersionFieldNumber to 1 // Only change if pbUseCustomDbVersion = True

             // This will create the DbVersion table automatically;

                   Set pbAutoCreatDbVersiontable to True

                   Set pbUseCustomDbVersion to False // Default = False. True = Use a custom DbVersion table 

oThere is also a new tool DUF Code Generator that can be used to take a snap-shot of the current development database and generate DUF code as a package file (*.pkg).

The easiest way to use the new interface is to remark your current cDbUpdateHandler object code. Then drag & drop a cDbUpdateHandler object from the Studio's Class Palette.

oThe most important addition is the new "DUF Code Generator" utility. It will generate code for your entire development database and save it to a package file. Compile that file into your program. When your program is run at customer site, the framework will compare it's content to the customer's current database and perform all necessary database changes automatically. The utility can also be used to generate code for just one or a selection of tables that has been changed. The file can then e.g. be send to other developers that work on the same system to make their databases identical.