Decision time is coming on the future of our custom-built VFP9 ERP software for our food processing operation. 20 users, 180 screens, 230 reports. Handles accounting, inventory, costing, scheduling, shipping, invoicing, ASN labelling and EDI.
For the last year I’ve been training a fellow (recommended by one of the owners) who is fluent in SQL and C#, in the ins and outs of Foxpro, so if I am hit by a bus, we at least have someone familiar with our system.
Our options are:
1. Do nothing. One comment on this site was that VFP9 will live as long as VB6 lives as they use the same libraries, and VB6 will be supported indefinitely.
2. Buy packaged software and accept the gains and losses of capability. And cost.
3. Rewrite. We are exploring converting to SQL Server, using C# for the logic level.
We would use Windows Forms for the screens and RDLC for the reports. These last two have been a real culture shock for me after the ease of doing forms and reports in Foxpro. I suppose I’ll get used to them—unless there are better options for reports and screens?
I’m tracking down choices for canned software, so my questions concern #1 and 3.
1. Is VFP9 safe, though not supported, as long as VB6 lives, though not supported?
It seems like Microsoft would have a hard time pulling the libraries VB6 uses.
3. Are Windows Forms for screens and RDLC for reports good options? I assume they’ll be supported for some time—don’t want to jump on the latest and greatest platform just to see it vanish next year.