>I'm in the camp that thinks there should be a demo version. Look how the public beta demonstrated excitement for the product. I've been pointing out some of the arguements that have been used in the past against a demo version.
>

This may be a heretofore unmentioned area where the more credible members of this community can agree to separately put forth untainted and unequivocal arguments to have the MS fellows who control the decision making process, or who have the power to decide and cause it's implementation, that a demo version of say version 8 be put out there.

Personally, VFP is one of the few programs that I have purchased wihtout first having a demo version, or a time or feature limited full version. I say go for the demo. It may be a heck of a stroke of genius in the marketing of VFP. Some say that the devil is in the details... should a demo version be put out, let it not be as limited as the demo versions of the different VFP frameworks I've tested. They are, by themselves, nowhere near what's needed to really enthuse many people who, while not of developer status, do have some understanding of what kind of output they should be able to produce with a product like VFP. (I should add that I am grateful to the companies who put out these version who when contacted did provide several pieces of documentation that do tell fully about the product capabilities.)

I see names such as your own, Jim, Alex, Bob, Tracy, Garrett, John, et. al. (too many to list) who if you make a decision to nudge and coax this idea along the proper channels, with a wink and a dose of objective reasoning, I'm sure can get this to happen... And there is no LOL about this. :)

P.S. Please forgive my "forwardness" (a word?), but I just couldn't hold back these observations on what I think is a good idea that should not be put out to pasture.

Thanks for your time.