>It may be two soon to know exactly what to do regarding the question this thread is asking. I don't know whether to jump on .NET, remain legacy, or what. Eventually I may be forced to do something even if its wrong.

Thanks Leland. The intent is to realistically find out the direction that VFP developers need to consider. The current state of "I dunno" can be overcome by looking at what developers really want both from VFP and from .Net. More important is the issue of satisfying customer need - which can be quite difficult - especially when they get to hear all about .net and more so if they read "The Decline of VFP".

Thanks again for your input.