I agree: it all has to work together. Which is why I keep peppering Samuel with questions like "are we going to have aselobj()" and "will aselobj() work from the Command Window." And I keep getting answers back as you have read here and in the Community Group (yes, and the Command Window will also have the ability to do Loops and Branching, i.e., multiline routines). And which is also why I find .Net so pitiful a development experience, even compared to a 5-year old VFP9 whose IDE hasn't really changed since what, VFP6?

I guess we'll see who buys the latte's <s>.

Hank

>Hi, Hank.
>
>Well, "succeed" would first mean: finish the job. (No disrespect intended.) My development efforts often follow the 90-90 rule. The first 90% of the project requires 90% of the effort. The last 10% requires an equal 90% of effort. And that for projects that I'm getting paid for! So just finishing the compiler functions for 100% (or close enough) of the Foxpro language would be remarkable.
>
>The rest of "succeed" is the intangibles. Does the entire language and UI work well enough to be adopted by a critical mass of developers? Or are there subtle "gotchas" that are ultimately discouraging?
>
>Time will tell and I am not asking for final answers at this point. I'm mostly trying to get a gut feeling from other developers as to whether this is a serious possibility for the future.
>
>Peter
>
>
>