![]() ![]() We recommend that you convert to C#.NET with a SQL database. You’ll have time to carefully plan the transition and add new functionality such as mobile apps. The larger and more complex your program, the sooner you should get started. Should I convert VFP to another language? We’ve taken over more than 200 programs and have become familiar with many different programming styles which is critical when supporting a program or converting to another language. ![]() We started with dBase II, then dBase III, then Clipper, then FoxBase, then FoxPro for DOS and Windows, then all versions of Visual FoxPro. We have specialized in Visual FoxPro since its very beginning. If you choose to stay, we can support you. Your current data (DBFs) will continue to be dangerously insecure. Not converting diminishes the value of your business. However, as fewer Visual FoxPro programmers are available, hourly rates will increase. Staying with Visual FoxPro will save money in the short term and you’ll continue using the program your employees know well. Should you stay with your current Visual FoxPro program, convert Visual FoxPro to another language, just add a SQL backend to your program or switch to “off-the-shelf” software? We have expert programmers that can help you answer: ERW Custom Programming specializes in Visual FoxPro support and conversion. One thing every owner of a Visual FoxPro program should be concerned about: the growing scarcity of qualified and available Visual FoxPro programmers. Some of you should begin exiting now some of you may have years before you need to be concerned. Microsoft ended all support of Visual FoxPro in January 2015. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |