Installation over previous versions

There are a lot of internal changes in the new version 3.00, but we tried to keep the upgrade the easiest possible.

1) It is better if you totally uninstall and delete any traces of the previous versions.

2) The templates changed names, so you have to unregister the previous version and register the new one. Open your template registry, and unregister any FullRecord 2.x template. If you still have the old templates on the templates folder, delete them. Then register the new ones (FullRecord.tpl and FullRecordLgcy.tpl).

4) Change your Audit files in the DCT. There are several new fields for the Audit file, and a new file. We recommend you take the Audit.DCT dictionary and copy the changes and new files from that DCT to yours.

5) After change the dictionary, make sure there are no empty fields in the global extension (As noted specially in Definitions 2 Tab).

6) Don't forget to convert your current audit files if you want to keep accessing them.

Note that you cannot use FullRecord 2.x with Clarion 5.5 or earlier. FullRecord 2.x will work only with Clarion 6 and later.

If you added manual code to audit embedded legacy code, you may leave it or remove it, that code will be simply ignored in this version (Otherwise you would be auditing the same code twice).

For Inserts: if the file has an autonumber key, now you will see the real behaviour of the program, which is and ADD operation with almost no data, and a CHANGE operation with the added data.

For Changes: the "Read" operation is no longer always necessary and it is not stored anymore if not, unless the ID field actually changed or there is no previous information (like when you "clean up" the audit file). The "old" read information can be left in the Audit file or it can be erased for shrink the database.

If you are upgrading from a version older than 1.80, then you need to import the new BrowseAuditField procedure into your app and the rest of the section don't apply.

The "BrowseAuditField" you already imported in version 1.8x into your app requires a new parameter. You need to change it from what you have now:

(*? AField,STRING SearchKey,STRING FileName,LONG MemoNumber,STRING ScreenPicture)

Add the new STRING ScreenPicture parameter both in "Prototype" and in "Parameters".

We are going to use a new field "FileVersion" in the audit files (Check the supplied DCT). The audit files will need to be converted to include the new field.

For implement the new "Field Inspect" feature a key in the Audit file needs to change. You need to change and convert your current Audit file in order to use the new feature.

The recording of procedures names was improved in this version. A global threaded queue is necessary for this change. You have to change the dictionary and point to the new fields in the General Tab. Instead of the single "procedure name" field in previous versions, now exists a queue with a single field (the procedure name inside the queue), with the following structure:

The "Inspect" procedures are no longer generated as local procedures. If you have the "View Record" control template populated in the Audit Browse, and you don't have the "Generate Global Procedures" option in the Inspect Tab active, you have to active this option for the Inspect Window to work. Previously if you don't had this option active, local code were generated instead of global code; now, no code is generated, thus you won't be able to inspect the stored data, if you don't activate this option.

The "View memo" new feature (enabled by default) for the inspection window requires a new button to be added to the window structure. If you don't want to use this new feature, you can disable it from the Inspect Tab.

There are many new features in version 1.50. However, they are not enabled by default, therefore after installation your programs should continue to work the same way without problems. You can enable the new features later as needed.

To enable the global compression feature, you need to convert your existing Audit files.

To enable the recording of the procedure name and workstation, you need to add new variables to the dct. You may copy & paste them from the example audit.dct file and convert your audit file as well.

Important: As the TPS example files changed, you should erase (or manually convert) your old ones prior to test the new examples, otherwise you will get and error 47.

As the global procedures now generate several procedures per module, delete the old .clw and .obj files prior to recompile to clean up the garbage. If you don't, you won't get any problem with your program but you will have some (probably a lot of) no longer used files in your folders.

If you have a custom TRN file, note that there are two new entries in it, they are:

An embed changed its internal name; if you had code in this embed, it will be as "orphaned". In that case you have to manually move your code to the embed again.

As the global procedures now generate with full long names, delete the old .clw and .obj files prior to recompile to clean up the garbage. If you don't, you won't get any problem with your program but you will have some (may be a lot of) no longer used files in your folders.

There are new variables that you have to define in the global template extension. Make sure to enter the Global extension and fill them before recompile your app.

If you are upgrading from version 1.0x you should change these variables in your own DCT as well:

Previous name	New name
FRGLO:COLA_Buffer	FRGLO:Queue_Buffer
FRGLO:Archivo	FRGLO:FileName
FRGLO:Registro	FRGLO:TheRecord

If you were using the "big dct" control and extension templates, you will see some errors upon opening your app with the new template (See "Generator: Unknown template type"). You have to delete the remains of those controls and repopulate the new ones.

If you install this version over a beta, it is recommended to uninstall the previous version first, before you install this one. Due to the big changes in beta versions and in version 1.00, if you already started to call the procedures from source code, please read the present manual before start to work with the current version.