>>>>>But then FoxPro 1.0 came it, and that changed everything.
>>>>
>>>>I was thoroughly un-impressed with FoxPro 1.0. I was more impressed with 2.x. And FoxPro for Windows 2.6 was amazing, but these also evolved on my getting-faster-over-time computers.
>>>
>>>Certainly, FoxPro 2 had SQL and Rushmore and that was big. But FoxPro 1.0 (and the events right after that) wound up crushing the competition.
>>
>>I was un-impressed by it solely because it was too slow on my slow machine. In fact, it was relatively awful.
>>
>>Back then, I didn't have the vision or understanding to realize that CPU speed would increase and what was slow this year in a couple years would be slow no longer. I began to realize that around FoxPro 2.x days, but I remember the first time we got FoxPro 1.x and tried it and I sat there thinking, "Seriously?" because it was just so slow. The popup windows were what made it slow. It had to render content behind other text windows, and scroll them using the CPU rather than the graphics card, or at least issue multiple scroll commands to work around the overlaid windows.
>
>I'm pretty sure Fox was always faster than dBase. :)
>
>>
>>FoxPro never did it for me. FoxPro for Windows did significantly. And when Visual FoxPro came out ... it literally changed my life by changing my thinking about software development. It took me a few years to fully grasp the object oriented nature of it all, but I was amazed at the way the event-driven design was presented, and with enhanced abilities added like BINDEVENT() ... just full-on amazing. It's why I've spent so much time developing Visual FreePro, and Visual FreePro, Jr. The best developer / runtime platform ever created for its footprint bar none.

Happy New Year