FoxPro2.6 Convert to Access and make GUI

You should - or rather must - team up with a local, skilled, and prominent Access developer with vast experience in ERP and accounting.

This is by no means a beginner's job.

Also, consider if it really will be worth the efforts. Perhaps you can by an off-the-shelf package which fits your business.

/gustav

We are running FoxPro 2.6

want to convert to Access with a GUI

When situations like this arise, I always like to do a Business Analysis of it before choosing a direction to take.

Especially in light of the fact that you are planning to

What is the reason for considering the not-insubstantial cost of converting (actually re-creating) what you have into a different language?

If you merely want to bring the old-appearing, old-feeling application up into the 21st century, you would be MUCH better off by converting your FP2.6 code into Visual Foxpro where a LARGE part of your existing code would be usable 'as is'.  

Help us to help you better by defining your Reasons for wanting to make this 'conversion'
Once we better understand those, we can better advise you as to an approach to take.

Good Luck

Thank you guys for the responses. The reason I am looking to change is, I want to get them off a 20 year old system. FoxPro 2.6 runs on XP and in order to get all machines on Windows 10, FoxPro has to go. This gives me an excuse to get rid of FoxPro for good. VFP, ended its life as well, therefore, I don't want to move to VFP even though it is super stable from what I hear.

I understand that going through the program codes is not a beginner's job and I certainly don't have months to do so. Keeping the big picture in mind, where eventually an ERP system will come in, what do you recommend I do for now?

Convert to Access?
Get a simple HR Payroll/Time Management software that later can be integrated in with ERP?

Thanks guys. Really appreciate the advice :)

Al

You are really asking for way too much. You don't even mention the size of your organisation, nor the business you are in. Or the country or language for that matter.

You would only get answers with so many precautions that they wouldn't be useful at all.

However, any solution will be expensive in either time or money and probably both. Until you are prepared and capable for such expenses, you may consider moving your FoxPro application to a virtual machine or a terminal server and use Remote Desktop to run it on users' Windows 10 machines. Cheap and proven.

/gustav

@Gustav - Agree mate. Virtual Machine would be an acceptable solution but the people using FoxPro are just so tired of the Dos based screens. Our company is 1200 people in the Manufacturing business.

@John - Thanks for the advice John. Access is what I am leaning towards as well. Will be doing an assessment with a company here to see how long and how much it would cost and based on that make a decision. Secondary option is to get a proper Payroll Software in place that wouldn't cost an arm and a leg but gets us into the 21st century

Our company is 1200 people in the Manufacturing business.

Oops. That, I would say, rules out any home-grown solution, indeed with a tight time schedule.

Usually, you would be a member of some trade association and/or business or local network. Quite often these have recommended and proven suggestions for payroll and HR software. Start there.

/gustav

Although 1200 are a lot that doesn't mean that Access can handle it....think it that way...till now your old FoxPro was handling it just fine...so if it was the age factor then probably you would continue to use it....so it's just about taking quotes from HR vendors for initial installation +server costs + support against Ms Access in the house..

Thanks for your suggestion guys. I did get quotes from vendors for a simple HR/Payroll systems, the company cannot go for those now, which is why I am leaning towards the Access way!

the people using FoxPro are just so tired of the Dos based screens

I can fully understand that.  And it is one of the reasons that I suggested that you consider moving your existing application up to Visual Foxpro
The interim re-create of your application into Access will be costly and not gain you anything in the way of additional functionality.

Access is a true powerhouse compared to FoxPro

Only a devoted Access developer would say something like that.
Foxpro and even more so with Visual Foxpro has historically out performed Access time and time again.

But if you want to spend a not-insubstantial sum of money to change your application on an interim basis to Access, go ahead.
However, note that for an interim change, the much more efficient and cost effective approach would be to upgrade it to Visual Foxpro.

Regardless of your choice - Good Luck

I agree with the others who said that rebuilding your app in Visual FoxPro would likely be much simpler than doing it in Access.  

I also agree with jrbbldr regarding the comparative strengths of VFP and Access.  I've worked with both and much prefer VFP.

You say you will "eventually ... get an ERP".  Is that far enough in the future that you will be able to recoup the cost of a temporary switch before changing systems again?