>Houston,
>
>VB does not compile to native code, nor will future versions.
>
>Walter,
>
>>>Probably VFP faster, many VFP objects are just simple drawings on form, when VB objects are real Windows.
>>>>are screen updated fast in VB than in VFP ?
>>>>Rajesh

---

I was under the impression that because VB is compiled to 'native' code it typically runs faster than VFP in most regards. The only area in which VFP excels (relative to VB) is in data processing - fortunately this is pretty much all we want to do in VFP ;-)

There is a related note 'Q258537' of Microsoft that explains how VFP 6.0 writes to the screen and Microsoft has confimed this to be a bug that has been corrected in Service Pack # 4, by supporting the switch BITMAP=OFF in the config.fpw file.

The explanation is, that when VFP writes anything to the screen, it writes first to an off-screen bitmap, and then performs a bit-block (bitblt) transfer to the screen. This results in smoother screen painting, but expecially in terminal emulation software in sever performance degration.