Hi DAW

We have found a problem in the full 14.1 where string type properties are
not consistent in the property sheets when handling non literal strings,
i.e. constants, global variables, file.field references etc..

At the end of the 14.1 test cycle Clive Richmond of Triumph reported a
problem where changing the Field_Mask, Field_Label_Long etc.. in the data
dictionary modeller which were constants were changed to literal strings.

i.e.

Set Field_Mask Field TABLE.Column To TA_MONEY_MASK

became

Set Field_Mask Field TABLE.Column To "TA_MONEY_MASK2"

When changing the value in data dictionary modeller, it should have been
TA_MONEY_MASK2 without quotes.

The fix in the full release of 14.1 was to disable entry to the option in
the data dictionary modeller when the value is not a literal string. This
is fine but the same rule has not been applied to the default value.

i.e.

Set Field_Changed_Value Field TABLE.Column To YES

became

Set Field_Changed_Value Field TABLE.Column To "NO"

When changing the value in data dictionary modeller, it should have been NO
without quotes. Entry to the field default should be disabled when not a
literal string.

Please note we have the following constants setup ...
Define NO as "N"
Define YES as "Y"


I have also seen a similar problem with psCaption of a toolbar item. See the
first reply for example workspace.

Open the only project, main.src. There is only one toolbar item and it is a
subclass. Look at the sublcass, cMyMenuItem (which is defined in the source
file), you'll notice that I am setting the caption and description in the
class to two variables which are above. However when you look at the
properties of the toolbar item object in the property sheet the caption and
description are set to the values of the constants and are enabled. I think
they should show the actual constants, C_MY_MENU_ITEM, and be disabled as
they are not literal strings.

Cheers
Tom