>Thanks Guys,
>
>You've made me understand the fact that I've been using an inproper meathod of programing code.
>I basicly use a form that has command buttons on it that relate to other forms that each have their own
>sub forms. They are all accessed via a DO FORM COMMAND and at the end of each usage I return to the
>calling program. I think you guys are saying that these forms are staying open, when my app get to long or stroung
>out it exceedes the limits.

I generally would not spawn another instance of a modeless form when one already is up and running, so that you have layer after layer of forms called from forms called from forms needlessly. You risk both DO NESTing - the situation where you've simply called too many things nested inside of a long and involved previous stack of form calls - and READ NESTing errors - READ NESTING results from having too many separately controlled layers of READ ineffect at once, like calling a modal form from a modal form from a modal form ad infinitum.

If lots of forms are needed, I'd try to launch a series of modelss forms that allow you to switch back context between several active forms, rather than having to spawn yet another instance of a form that already exists and is active from inside a child form.

>It sugests that I should close forms and procedures as I go along outward in my app from the main menu form.
>Am I on the right track ?
>
>John