setting existing customproperties

[J. Landman Gay]

On 8/1/13 4:50 PM, Dr. Hawkins wrote:
> I've been setting custom properties of fields willy-nilly for some
> time now without a problem.
>
> I tried on stacks today, and failed.
>
> Reading the dictionary, it appears that I should be using an array.
>
> Is being able to set a custom property of a field a bug, or am I
> missing something here?
>
> (e.g., I have some fields with a custom "textClr" property from typos . . .
>

I set properties on stacks all the time, it works exactly like setting 
them on a field or any other object. You don't need to use an array 
unless you want to store an actual array without combining it first.

What happened when it failed?

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com