>>Using Mark's suggestion you will create a public array. I have a rule to avoid public variables if it's possible. If you need your array for this control only, you should create this array as a property of your control and not make it public.
>>
>>First of all, you should decide, what would be the scope of this array, then you will use the suggestion, which is appropriate. I & Eric understood your original post, as you want to make your array accessable everythere in your application.
>
>Thanks Nadya,
>
>Yeah, I stay away from public anything. Use properties when possible. :)

I do use a goApp object to store globally available properties in my apps instead of mem vars. I probably should have suggested that, but based on his question, I could not assume he had such an object. Next time I'll ask anyway. :-O