>I was contacted by a potential client who is still running some legacy FP 2.5 applications, and they are inquiring about what it will take to convert them to VFP. Their IT people are telling them to convert it to Access (groan) They have 5 users who are intimately familiar with the program, but are not really programmers. They do consider the application as mission critical.
If your customer like more stable and profesionall application with possibility to migrate to SQL - VFP is the choise. If they like cheapest solution, and their IT people are enough familiar with Access let's go in this direction.
>As I recall, with the introduction of classes, methods, events, etc, the best practice was to completely rewrite the app so as to take advantage of improved functionality and newer features inherent in VFP, as well as compatibility with current operating systesm. My old experience with conversion wizards rarely produced anything but junk.
You are perfectly right my 3 years expereince of converting old FP2.x, Clipper or dBase legacy system to VFP/SQLServer shows that we can keep some of datamodel, sometimes it needs improvements depend on GUI which you will use. You can keep some busiines calculation, but all other should be rewritten.
>The little voice in my head tells me that this is still the case, and I guess I am looking here for confirmation before I start writing a proposal. My most recent work has been with Oracle, and I have been away from VFP for a year or so
You get already confirmation and can start riting proposal-:) If you have any other questions you are welcome.