>Not putting code into forms is a mistake in an OOP environment. However, presumably, lots of code should be common to many of your forms. So your first step should be to develop some form classes that contain all the common stuff. Then base your forms on those classes.
>
>Tamar

Tamar,
There are two reasons we use our current method of calling a prg that runs the form:
1 - Much easier to maintain the code as it is all in one prg and not in some number of methods that must be opened seperatly.
2 - It decreases the size of the final .exe which now is approaching 10 MB.

What is the difference between putting code in a form and having the code in a prg as far as OOP is concerned? I thought it would be the same.

I realize our method of calling a prg which calls the form could be the reason the modeless forms only flash and disappear but that can be solved.

ps. I have a number of your books and could not have gotten this far with FoxPro without them.