>>> John, if you have time could you give just a little more information on what this does, etc.? I couldn't follow the information I found due to language issues.
>
>VFP10 currently is primarily a bug fix/future-proofing exercise. If you have VFP9 installed and service packed, run the VFP10 installer and it builds a new and separate VFP10 from your VFP9 without interfering with the VFP9 setup. IOW as long as you have VFP9 you can try this without breaking anything. Then if you use VFP10 for your IDE instead of VFP9, you get various bug fixes that also appear in your VFP10 distributed apps. E.g. the fix for the notorious reporting header bug may be of interest to a lot of people. Also there are some quiet improvements for Win7 compatibility and the ability to include inline assembly or C++ in your VFP code, meaning you can extend your vfp apps in practically any direction. Next, there's interest in a 64-bit version that may not be quite as difficult as we we were led to believe. And finally, Chen is asking for a wishlist on what to do next. My experience of Chen is that for him a wish list isn't wishful thinking, he really is asking what people would like him to do next. My advice: let him know what you'd like to see. Certainly can't do any harm.


1.) "inline assembly or C++ in your VFP code" - I thought we could do this with FLLs
2.) 64-bit is slower for programs from what I've heard but can be faster for data if you have hugemungus data. and how the heck is this guy gonna support all the exotic bugs sure to arise in a timely fashion (if you thought MS was bad???). That is IF he get's to it..
3.) what's the web and mobile story??
4.) is it really foxpro with Rushmore, speed, etc.
5.) meh .....