>
>I suggest using an array (or a collection) for properties related among themselves. For example, an array with references to all open forms. If you have unrelated properties, it is convenient to be able to access by name.
>
>As to get and set methods... I understand that in Java, for example, this is the recommended practice, to encapsulate (hide from other parts of the program) details about the internal workings of the class. However, in Visual FoxPro 6 and later there is another way to do this - access and assign methods. In other words, you may decide to store a value in an object property, which has a certain name, type, and data structure. But if you later decide to change the internal workings of the object, you can intercept calls to the object, from outside, with access and assign methods - and store the information in a completely different way - without having to change programs that call it.
>
>Now, I don't know whether this is a "recommended practice", but it does give you an alternative.

Thank you, Hilmar. Very helpful input. Especially about Access and Assign methods. Although, in this case - what seems to be pretty straight forward - I was thinking about getting the value of the array (or collection) property directly from the application object. For example:

cMyTableName = oApp.aMetaTableName[2]

Of course the array element number can be used as a name in .H file.