|Joined: 12 Mar 2004|
|Location: Omaha, NE||
|Version 1.20 (10/18/2007)
ENHANCE: When adding/changing/activating a field in the Field Encryption
Registry (which has triggers), make sure that the trigger names
do not already exist on the file. Also make sure that the Insert,
Update and Delete trigger names are unique.
ENHANCE: Make an audit journal entry when the activation or deactivation
of a field registry entry fails.
FIX: Fix the CHGFLDENC command to show the correct value for the
"Trigger name for updates" parameter.
FIX: When activating a field encryption entry, check to see if the
same field name is already activated (after allocating the file).
FIX: When generating backup save files (for certain maintenance
activities in the product), make sure that when creating the
auto-named save file, that the library list is not used to
determine if the backup file already exists. Just check the
FIX: When storing encrypted values in an external file, make sure
an alpha index number (which utilizes all 13 positions) is
correctly parsed for encryption and decryption functions.
FIX: Allow calling the F_DecFld function and the P_DecFld stored
procedure from SQL even if the field registry entry has
FIX: Fixed the Field Registry Activation process to resolve the trigger
library name of *DBLIB to the database library name. This is
when trigger names are overridden by the customer (not *GEN).
FIX: Fixed problem in F_GetEncFld function to properly format the
numeric decrypted value.