Fat Fingers again today :o)

My intention was to write that I have seen far more poorly designed Access apps than VFP. I have seen a lot of badly written code in older versions of Foxpro, but not as much in VFP. I think as the product matured, so did the developers :o)


>>I've seen a lot of poorly amount of bad code I've seen in Foxbase/Foxpro/VFP doesn't touch the amount of poorly designed Access apps I've had to fix!
>
>Eh?? Could you maybe try that on me again, only in English this time? ;)
>
>>
>>
>>
>>>>It has been my sad experience that the vast majority of VFP "programmers" lack even the most rudimentary of competent programming skills. Perhaps that is the reason so many are fighting so hard against learning new tools.
>>>
>>>I kind of agree in that VFP, being so powerful and at the same time fairly simple to pick up, can allow untrained developers to get some sort of solution out there. The same could be said for VB (before .NET).
>>>
>>>It takes a little bit more technical skill to develop in C, C++ or C# and VB.NET but this shouldn't be confused with good development and design skills.
>>>
>>>I've been appalled at the type of code that I've seen produced in C++ in the past. I've seen a lot of "look how clever I am - I can get 3 things to happen in one line of code" or "only I'm smart enough to understand this 800 line function that I just wrote" type of code out there.