>The issue of testing forms from the command line is something I hadn't thought about. I'm not in the habit of doing that because I work in a very large system in which the object model we're working under requires a boatload of objects being instantiated anyway, so it is near impossible running forms outside of the foundation.
>
>I'm going through the excercise of building my own framework for learning purposes/self-projects, so this is something to keep in mind.
>
>I agree that placing the proc-class would not be beneficial.
>
>hmmm..what other issues are lurking out there?

Jim,

You might want to visit www.hentzenwerke.com and check out the VFP6.0 books there. I am co-author of one on Essentials of Application Development in VFP 6.0. There are chapters in that book that specifically deal with how to make your framework and form classes so that the forms work in the framework but they also be run without the framework.

There is also an example of a startup program that allows you pass .T. to it and it will drop you back to the command window with your project open while the app is running. You can edit and run forms or anything else without rerunning the app.

There's alot of other stuff in the book too. Most of the book applies to VFP5 as well, except, of course, those features that are new to VFP6.