Maybe someone or a team should come up with a standard guideline. Since the goal is to have a 'sample VFP application' it should be simple enough for new developers to follow along with yet demonstrate vfp's features and NOT break any standard OOP or ntier rules if possible (without adhering too strictly to some of those guidelines out there on ntier development) which can be limiting to say the least... Perhaps it should strictly be a client-server or desktop app then? Or a desktop app with an optional ASP front end (for advanced users to learn)? The possibilities are endless. What would MSFT like to see in the sample app if they could invest their resource in it without taking away from development time on Europa? Maybe a MSFT person could participate simply for providing guidance on the goals and standards to be incorporated in the sample app? That would not require any unreasonable time involvement on their part but still help to ensure the sample app would adhere to MSFT's goals...


>>Since MSFT has limited resource devoted to VFP for business reasons, but many VFP developers use it as their primary source of income, perhaps a group of UT VFP developers could get together and design a really good VFP Sample Application that will both show good design strategies and also show off VFP's features. Sort-of like the UT competition we had not too long ago where each country had a team? We all really enjoyed it and benefited from it. However, instead of a 'speed race' this time we could have a set but reasonable time frame and maybe more would participate? I think while many think this should be MSFT's responsibility, we ALL would benefit from it regardless of who does it as long as it is done right...
>>
>>
>Now we can argue, “Should it be form centric or container centric”? :)