>Our company currently has an established product written in FP 2.6.
>It has been decided to go a little different way and use a SQL based data engine such as Oracle or SQLServer as the backend with a separate product for the front end. Some of our major stock holders are pushing for the front end to be written in VB. They want this because they perceive it to be a better more stable language than VFP.
>I have been asked to list some pros & cons of VFP versus VB. I don't know much about VB so if anyone can give me some help in this area besides the obvious that switching to VB would require basically starting from scratch. I have already done several conversions from FP2.6 to VFP so I am aware of the problems this can cause.
>TIA
>Mike Yates

I guess the big question is, what are stockholders doing making technical decisions? VFP is here to stay...and will be for a long time. It's nice that you want to access C/S backend, but what are you going to do with the data once you have retrieved it? VFP definately outdoes VB here. VB was designed to handle data. VB was not...it is a general purpose language. There are several VFP success stories on the VFP web site that may be of help.