Thanks for giving it a shot - I appreciate your clarity, particularly about what you aren't sure of. Okay, what I mean by the four disabled modes is like this... When forms load, each of the controls generally calls a function in its Init code to load it into an array. The method should be saved in the form class. The method makes arrays, depending on the control's settings, which tell it whether a control's Enabled property ought to be .T. or .F. in certain conditions. For instance, when a new record is being added you might want the Search, Exit and Navigation buttons disabled as well as certain fields on the form. When the conditions change - like the user presses Add or Edit, another method is called which examines the array and Enables the appropriate controls.

The conditions may include:
1. Add Mode, as I have explained above.
2. Edit Mode - which may be an explicit Edit mode where the user has to press Edit to change any fields, or it might be that you are by default in Edit mode.
3. No Records Mode - If the main table for the form is empty, should such-and-such a control be enabled.
4. Programmatically Disabled -- I do not have this feature in my (temporarily) piece of junk architechture, but it seems useful. It should not be loaded into an array but checked during the method that disables controls. If this control property is .T., the control should be disabled regardless of the settings of AddMode, Edit Mode, etc. The reason this is important is since you have this method resetting your Enabled properties all the time, you need a way to access it yourself.


>>3. Does it load an array of controls including whether they should be enabled in Editmode, Addmode, No Records Mode, and some sort of Programmatically Disabled Mode?

>Sounds like I could learn a lot from the background of the question. Could you elaborate?