>>If your main concern is "procedure libraries", then I would use the .NewObject() method or NEWOBJECT() function to add or instantiate .PRG classes; you specify the .PRG as one of the parameters.
>
>No my concern is one of standard programming methods. Most if not all of my old proceedure codes have been ported to classfiles, (mostly non visual class files) mainly for application deployment purposes. I find distributing class files, over network is that much eaiser (or the internet for that matter) I would like to somehow get away from using .prg's at all.
>so I guess its just how I pack up some code... the cleaner and fewer files, and more self documented, I like. dropping a non visual class, wich is needed on a form or two.just to me makes more sense these days than having to remember where I put that .prg.... so ya. I am getting picky.

Funny. I hate SCX's and VCX's; I specifically use a VCX/SCX to PRG converter. I only use the SCX/VCX Designer to "paint" Forms and Controls; then I run them thru a converter to create .PRG class/component libraries that are subclasses of other "code-only" classes. I prefer to see all my Classes and Forms as .PRG's.

Anyway, Tom Rettig did some work in this area and put it in the public domain; there was a program called PRGTOVCX.PRG. You might find the source code on Compuserve; it may also have been included on CD with some of the earlier VFP books.