The custom properties that you create in Meridian can be used in VBScript expressions and custom client extensions. However, because of a limitation of VBScript, the naming of custom properties is very important. VBScript does not support the concept of property sets, which are a part of a property's definition. The property set name is also required to fully specify a particular property in custom extensions in the Meridian Developer Edition, which is used to create extensions. So, a workaround is necessary for compatibility with VBScript. This is provided by the VBScript name option of a property.
When you create a new property in Meridian Enterprise Configurator, and assign it a name in Display Name, Meridian Enterprise Configurator calculates a default name (without spaces) for use in VBScript and displays it in VBScript name. It calculates the name according to the following pattern:
<PropertySetName>_<PropertyName>
You can change the name or accept the default name.
The VB Designer name option contains the default name, which is the same as the Display Name in a Visual Basic designer. You can change this name or accept the default name.
