>>>You mean you became too good for the product ;-D
>>
>>That will ever happen:). I do sometimes have the sense I can do anything I imagine with VFP:). Thats Okay as long as we have good coding standards. Maybey VFP 8 is easily confused when forms, DBFs and PRGs have the same name. Maybe the fix would be as simple as renaming form "SoAndSo" to "frmSoAndSo"! The only contention (then) would be "SoAndSo.PRG" and "SoAndSo.DBF"!
>
>I'm actually using this in development. Several forms reference a property from the application object - which isn't around at development time. Instead, I open a .dbf with the same name (goApp) and fieldnames that contain the values I need them to. Works good for me. :)
>
>Chris.

Go Ysleta! The issue turned out to be the function used to vette for prospective objects. I was using VARTYPE. The switch to TYPE [seems to have] cured it! I like using forms and PRGs and DBFs that have the same name!

When I use PRG form classes - they are all "active" from the start. I just hide or show as needed at runtime. Your idea seems clever!