Bug Fixes
- Auxiliary Files (SCRIPT and DATA Sections): Fixed access violation that would result when loading DynamicFormatting object types from an aux file and fields specified for the Context Object are not supported for that type of object. These fields are just skipped with an error message written to the log.
- File Formats: When an advanced filter condition is using a field instead of a value for comparison, the field will be stored internally using the location number instead of the field name if using the option to show variablenames using names instead of location numbers. This affects fields like custom expressions, custom strings, custom integers, etc. that can be named. Previously, the internal storage could change based on the option setting and could result in the field not being found when loading a PWB with saved filters. This will keep the internal storage consistent regardless of the option.
- User Interface Dialogs: Fixed a bug with the Advanced Filter dialog when a filter includes a Use Another Filter condition, certain circumstances could result in mislinking the target filter.