I'll tell you my own experience, living in a country where people do not usually allocate big resources to programming.
I have apps written in vfp6 that I upgraded (changed a few things like select commands and reports, plus some gui things like grids) to vfp 9. No big deal, really, just a couple weeks of conversion work, that's all. As for vfp apps running on windows 7, my clients have a variety of windows boxes (XP, Vista (excuse the bad language), W7 in all flavours, event windows server 2003/2008) The VFP apps do not care at all in which OS they sit. They just work as usual. The trick with W7 is to kill the UAC. You are the one to control what users can or cannot do with their files, not Microsoft. The rest is just based on how well you program your application. As for the support issue, some people in this forum already told you their views and it's up to you what to tell your client. But in general, you should make sure they trust YOU (or YOUR company, whether a one man operation or a community of programmers) to solve whatever issues may present themselves as time goes by. To give you an example, some of my clients are now considering RDT, virtual networks, etc. And it is up to me to upgrade my knowledge and give them the answer they need for their particular circumstances. Of course, you should try to get into the NET world (if you are still young and have many years of programming ahead of you) because you can't swim for a long the time against the current. But that should be a long term project for you. In the meantime, while you reach a considerable height in your learning curve, and feel confident that you can make the leap to another language, you must give your client the assurance that whatever issues present themselves, you will be able to provide a suitable solution for them. Otherwise, you will be replaced as easily as they would replace their old car. My two cents, anyways Rafael Copquin El 24/04/2011 18:38, Jon Westcot escribió: > Hi all: > > I have been supporting, for ten years or so, a VFP6 application that I > developed for a company. They are looking to upgrade their machines to Win7 > and have been having trouble getting the VFP6 application to install. I > have not yet had a chance to test this out on my own, but I suspect that the > issue could quickly be resolved by using the Win XPmode procedure discussed > elsewhere. > > Before I knew about that option, I suggested to them that upgrading to > VFP9 might be the way to go to resolve these issues. However, that was a > mistake, as they discovered that -- gasp! -- Microsoft has discontinued > development of VFP. > > So, NOW they're asking me if I would recommend that they stay with VFP > or if they should move to something else that will be supported in the > future. > > Now, I could easily (well, not EASILY, but you all know what I mean) > begin rewriting this application for something else, such as a VB/SQL > combination, but frankly, that's gonna get ugly fast. The VFP app is solid > and has been working well for them for a long time. I suspect that they > could make the minor investment for me to move the app from VFP6 to VFP9 > much more easily than they could move to an entirely new look-and-feel > application with an entirely new back-end database that's not integrated > into the development language. > > But, is that the PROPER answer to give them? > > I'd really enjoy hearing comments on all sides of these questions... > that is, if you all don't mind chiming in. The best VFP minds in the world > comprise this audience, and it would be quite beneficial for me to read > various thoughts on this topic. > > Thanks in advance! > > Jon > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
