>...
>>>Now, whether WinDev can handle everything that VFP can handle - I cannot categorically say yes only because I dont know everything VFP can do, I dont know everything WinDev can do, I dont know everything that you are doing in VFP, etc. In other words, there are too many unknowns for me to be categorical in my answer. However, I would be willing to wager the answer is yes and even give odds that it can do everything and much more than VFP can.
>>>
>>>.
>>
>>Jos, are you of the opinion that VFP was used by the WinDev people as a basis for their shipping product (easy to use.design/ etc. etc.)? Or was VFP developers targeted by WinDev once it became clear that VFP was at the end of line in development?
>
>Mel
>
>I do not know the exact history of WinDev (although I could find out as I know (online) a number of developers who have used it since the first versions) but due to the incredible number of similarities between the syntax and the way you build the projects I believe both VFP and WinDev have their origins in dBase/FoxBase. There are just too many similarities between the two languages.
>
>In fact so much so, that to answer Dragan's question a bit further, I believe it would be possible to write a code convertor from VFP to WinDev if one had the inclination to do so. We did not do this because (1) we are not uber-experts in VFP or WinDev, and (2) the convertor would take us longer to write than just manually doing the conversions, and (3) we wanted to re-factor our VFP code, clean it up, etc. But I believe you could literally do a one-for-one conversion i.e. duplicate each form, each report, each query, each procedure file, each function, etc. and I think you could do that with a high degree of maintaining a 1:1 relationship. The upside would be you would then be in a modern 32/64 bit IDE with access to very many more controls, functions, productivity enhancing IDE, and all the other things in WinDev, plus get an upgrade every year.
>
>I do recall now, I think - not 100% sure, that there are 2 areas of WinDev that WinDev developers generally do not seem to like. If my memory is correct that would be the RAD (rapid application development) features of WinDev and the Source Code Manager. I repeat I am not 100% sure I am correct but I think that the feeling is that the RAD features (where WinDev can build forms and reports from the database definitions) are not good enough for commercial app development and one should not go down that road (we did not). And I think the Source Code Manager might not be 100% up to the job (and we dont use that either as we have our own backup and restores processes in place and have only a very small team of developers).
>
>.

Jos, thanks.... all very interesting and helpful.