You'll need _base.vcx if you're using any class that's subclassed from it. All subclassing in VFP happens dymamically. For example, if your base form has some code in the Init and your subbase doesn't, VFP won't have access to that code if it can't get at the base class. I try to keep my class libraries pretty small (as in not too many classes) so at least I don't have to bring in dozens of classes when I just need a few.

>Hi folks,
>
>Well, I'm finally making the jump into VFP due to a small project we need done and it seems like a good opportunity to bury the "learning curve" into this particular project. I'm making a HUGE jump considering up to this point we've done everything in FPD 2.5 <g> So, I don't doubt I may be asking some stupid questions now and then - so I'd figured I'd get started off with a bang.
>
>I began this project by subclassing all the classes in "_base.vcx". I only have one form so far in this project. I made sure that the form itself and all the controls on it are based on my own classes. However, I noticed that when I rebuilt the project it sucked in "_base.vcx" anyway. AFAIK, I'm not actually using any of those classes directly. Does this file come in since it's the parent to all my classes, or did I mistakenly use a control somewhere wasn't based on my subclasses? Just wondering if I can avoid having "_base.vcx" in my project somehow.
>
>Thanks,
>
>Joe