Field.CreateProperty Method
| Access Developer Reference |
Creates a new user-defined Property object (Microsoft Access workspaces only).
Syntax
expression.CreateProperty(Name, Type, Value, DDL)
expression A variable that represents a Field object.
Parameters
| Name | Required/Optional | Data Type | Description |
|---|---|---|---|
| Name | Optional | Variant | A String that uniquely names the new Property object. See the Name property for details on valid Property names. |
| Type | Optional | Variant | A constant that defines the data type of the new Property object. See the Type property for valid data types. |
| Value | Optional | Variant | A Variant containing the initial property value. See the Value property for details. |
| DDL | Optional | Variant | A Variant (Boolean subtype) that indicates whether or not the Property is a DDL object. The default is False. If DDL is True, users can't change or delete this Property object unless they have dbSecWriteDef permission. |
Return Value
Property
Remarks
You can create a user-defined Property object only in the Properties collection of an object that is persistent.
If you omit one or more of the optional parts when you use CreateProperty, you can use an appropriate assignment statement to set or reset the corresponding property before you append the new object to a collection. After you append the object, you can alter some but not all of its property settings. See the Name, Type, and Value property topics for more details.
If name refers to an object that is already a member of the collection, a run-time error occurs when you use the Append method.
To remove a user-defined Property object from the collection, use the Delete method on the Properties collection. You can't delete built-in properties.
.gif "Bb243056.vs_note(en-us,office.12).gif") Note |
|---|
| If you omit the DDL argument, it defaults to False (non-DDL). Because no corresponding DDL property is exposed, you must delete and re-create a Property object you want to change from DDL to non-DDL. |
See Also