>I'm on a fact finding mission and I know this is the place to find the answer. Was VFP Micrsoft's first OOP programming language? I know VB (prior to .NET) was object based, but was VFP Microsoft's first OOP language offer to the development community? If it wasn't where in line did VFP fall regarding OOP?
>
>Thanks so much!
>
>In additional to Microsoft's C++, they briefly sold QuickPascal (in the late 1980's, around the same time they were pushing things like Quick-C).
>
>But around those times, Borland was often pioneering ahead of Microsoft in terms of OOP and development languages
>
>Out of curiosity, what's the significance of the question? (other than simply for historical reasons)


Thank you, Kevin for your response.

The reason why I asked this question is because I'm currently working at a shop right now where they are doing a VFP->.NET conversion. I'm trying to educate the IT Director of VFP/OOP capabilities. I finished my .NET certification but don't have a lot of experience at this point. I've used a VFP OOP framework (Visual FoxExpress) since 2001 where n-tier concepts and OOP were used extensively in the framework. It was the first time the light bulb actually lit up for me regarding OOP concepts even though I took OOP concepts and design in college. I never quite "got it" until I started working with VFE (thanks Mike and Toni). Every VFP/VFE application I ever created utilized a SQL Server backend and keeping the presentation layer, business layer and data layer separated made development so much easier and just made a lot more sense.

What helped me the most with my .NET certification was years of VFP development using n-tier design concepts and OOP and Kevin McNeish's book, .NET for the VFP Developer (sorry if I messed up the title, don't have the book in front of me). If a VFP developer was fortunate enough (as I was) to develop VFP applications from scratch using a framework that utilized nearly exclusive VFP OOP concepts as well as an n-tier approach, I'm sure it had to help make the transition to .NET easier.

I'm trying to convince him that I just don't think moving to the .NET team would be that much of a leap for me and I'm trying let him know that VFP had OOP technology (whether or not it was used to its fullest was in the hands of the developer). I thought I could provide him with a little history lesson regarding VFP, information I'm sure he has never been exposed to in the past.

Bottom line, I'm trying to convince him to give me a shot instead of letting the VFP developers go once the conversion has been completed.

Thanks again for your response.

James