Hi John,

I agree totally. The last project I worked on was a VB-Access app (with VB as the front and Access as the back-end). I enjoyed using VB (employing ADO recordsets and the such) and currently I'm spending alot of time learning more about VB for the exact reasons you have mentioned.

Unlike you, I would be a bit disappointed if VFP were go away, because I have used the product for years and it has served me well. I guess the good thing with this whole issue is that manipulating data through VB has improved significantly with ADO and in alot of ways is very similiar to using cursors in VFP - so the learning curve hasn't been as difficult as I expected.

>Hi Allan,
>
>This may sound extremely cynical, but if MS dropped VFP I don't think I would care in the long term. I would have to slowly evolve my existing supported applications to (VB or Access) and (MSDE or SQL Server). If VFP is no more, doesn't mean I suddenly stop being a programmer/analyst.
>
>I'm a VFP "homer"; I defend it and it's developers to the "n"th degree, but it would be kind of foolish not to be at least conversant in other tools and techniques.