Agree, specially about speed in general. Really, it have so little difference between VB and VFP (remember - both are parts of Visual Studio), that it should not be the criteria of selection VFP over VB or vise versa.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>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 tend to agree with you Vlad. But it's worth pointing out that if a VB form's AutoRedraw property is set to True, it also retains bitmap copies of the forms, in addition to the real windows objects, to speed repaints. This takes up more memory but increases speed. Also, the ClipControls property in both languages will have an affect.
>
>And of course, are we talking about bound or unbound controls? Do the screen updates Rajesh refers to include data updates?
>
>My hunch (not scientific, just an educated hypothesis) is that in a typical VB app compared to a typical VFP app, the underlying code in a form, and the various property settings (especially the ones I mention above), will probably have enough of an affect to cancel out any of the "isolated" performace gains that one language's visual refresh has over another.
>
>Put another way, I don't think that "isolated" speed is enough of a factor to determine which language is best suited for the task at hand; or, certainly, it should be pretty low on the list. (Not sure if that is why Rajesh is asking, but it seems worth stating).