Fortunately I don't always have to be right :) But it is going to be
a long time before every application built uses xHTML as a serious UI, and if
your going to use VB as a UI you might as well stick with fox and keep
your debugging and deployment requirements in check. xHTML is a document display protocol not designed for data entry. The best we can do is 'tack-on' data entry capabilities, but it pales in comparison to what users expect from a windows application.


>HiI Ed,
>
>>These things seem to fit in with MS plans of thin-client and Terminal Server deployment. Current VFP screens cannot be transmitted by the T/S engine as efficient as other languages.
>
>The oficial placement of VFP in VS is as a middle-tier component. For UI, you should use a "thin" client like VB or HTML. Every demonstration from Microsoft shows this. I'd rather expect improvements in the way OLEDB and ADO are accessed, better integration into MTS, better support as a COM/DCOM server. The new multithreaded DLL is one step into that direction, enhanced COM support is another.
>
>I really doubt that Microsoft would spend much time on improving the UI in a way that we can use as developers.
>
>Christof