Jeff,

>There is no downside here. Whatever unfolds, we will still have a great tool and if the CLR succeeds, it will be that much easier to add VB to our skill-set.

The primary downside I see right now is market perception, but hey -- most IT managers already have written off VFP, so I don't think it hurts us that much.

VFP7's ability to play inside and outside of .NET means tremendous flexibility. I for one, would not want to see us inextricably bound to the CLR, but am interested in pursuing creative ideas for compile options to the CLR to give us the best of both worlds.

As I heard someone remark today, there are about 5 or 6 major aspects to .NET, and VFP7 can play in all of them except for the CLR, so we really are in a very flexible position.