>Ok I admit, I have sinned. I use global variables in the FPD app that I am converting to VFP.
>
>Now the question, where is the most logical place to keep those values in VFP? I assume as properties of some object, but which objects?
>
>1) There are values related to the calendar e.g. Days of week or names of months in spanish. You may consider these to be "permanent" values.
>
>2) Values established by law for all clients. I keep many of these in a table, but I find it better to load them up to memory and work from there since table isn't always in right record. Perhaps an object which represents that table?
>
>3) Values that have to do with this customer, such as what options they paid for. Perhaps oLicensee (?)
>
>4) Values that have to do with the company (user may have several). oCompany (?).
>
>Suggestions, please.
>
>Alex
A custom class generally named oApp is a nice place. oApp could have arrays for some vars, obj refs, table open/close routines, license checker etc. Array would be especially good fo enumerating Spanish day, month etc names.
Cetin
