Mike,

Thanks for your thoughtful response. I had thought about the 1-function per prg idea and the old problem of performance, and I guess if you're building those for use with earlier versions than VFP6 SP3, it would be a problem.

It just seems to me that the one-line approach is more consistent with what I see in the other VS languages, and in all the books I'm reading about distributed nTier development, with examples in VB and VC. I also think I like the looks and readability of the one-line style.

As we move more and more between various languages the consistency of that approach appeals to me.

>For the above reason, I wish VFP could create classes visually without storing them in a VCX. That way I could say CreateObject("blah") and if blah.??? existed, the object would be instantiated without first having to say set classlib to blahlib.vcx.

That would be nice. I've been using NEWOBJECT's 2nd parameter a good bit to point to the correct prg containing the Session-based class I'm instantiating in order to avoid SET PROCEDURE.

Would you have them stored one class per file, dbf-style, or as .prg-style text classes?

>Anyone care to suggest a file extension for classlib-less classes?

How about:
.cll (classlib-less)
.fxc (fox class)
.dwc (doit with class)
.ith (instantiate this)
.nxb (not xbase)