>>>>Without a native compiler, VFP is dead. The only people keeping it alive
>>>>are the people who can give lip service.
>>>>
>>>so to follow this logic - without a native Compiler JAVA is dead etc.
>>>
>>>Arnon
>>
>>Internet Explorer does have the JIT compiler, but even this is cannot render an app as fast as a Delphi compiled exe.
>
>Mr Asif,
>
>Sorry to ask you such a simple question but can you pls tell me what is the meaning of Native Compiler ??
>
>TIA

Take a look at Delphi 3 or Visual C++. Then write a simple application in VFP, Delphi3, and Visual C++ and compare how the three versions run on a 486 DX2, a P75, a P90, and a P133.

Believe me, I still feel VFP has the best development environment, but the execution speed of it's apps suck. I know that the common answer from most developers is get a faster computer, but my experience with the companies I have dealt with is frustration and loss of faith in the development team from Marketing departments, and Project Directors who quitely write-off 6 months, 1year, and 2 year projects. Even after telling them two weeks into the job that VFP was not suitable for what they were trying to do, I allways had a smooth talking IS manager who would dismiss my statements even though my VFP experience was superior to theirs. Off-course, when the time for evaluation came, I could always say 'I told you so...'

A native compiler produces compiled code from within the development environment that you are using. The compiler that I'm talking about in this case is not VFP's native interpretive compiler but a compiler that produces true object code so that the machine can execute instructions directly without having to evaluate VAR TYPES prior to execution.

If VFP were to aquire a native object code compiler, there would be a massive database market shake-out with VFP as the winner. Unfortunately I still see too many votes accepting the product in it's current form through VFP purchases.