Upgrading FoxPro for DOS, what would you recommend?

[pixiepoet]

I am a newly hired Network Administrator who does not know FoxPro 2.5 programming language. This company has used FoxPro for almost 10 years, using it as a base for proprietary custom made applications.

We have recently upgraded various software and hardware and now we are running into problems with integration and compatibility with this new software (Win XP, various software, and printing). Other than not knowing how to program (let alone troubleshoot) FoxPro, I thought it best that we upgrade it to some easier software that even a non-programming dummy (like me) can handle.

We have a small 8 person company that contracts construction-related jobs for about 20 manufacturers and hundreds of clients. We use the FoxPro in conjunction with AutoCAD to estimate the costs of each job, do structure analysis, print out reports, and keep track of clients and jobs and products ordered. We are running off of a NetWare 6 server with Windows 98 and XP workstations, and have 4 printers.

Anyone out there with expertise in upgrading: What software would you recommend to upgrade to? Is it possible to upgrade to an easier software that even a non-programmer like me can maintain?

Any help would be appreciated. Thank you.

 

[JRB-Bldr]

If you are looking for a recommendation for a totally Non-Foxpro language, this might not be the best place to post your question - being that we are primarily Foxpro (in one form or another) advocates and "evangelists". However, there are a couple of newer Foxpro versions which you might wish to consider - both FPW and VFP are compatible with Win 2000 and Win XP.

The complexity of your application could be a very big factor to consider when reviewing where to go. Some languages handle complex data manipulation well and others have a more difficult time of it. The Foxpro languages (FPW & VFP) all are excellent at handling data (and most everything else). Where VB primarily depends on all but the most simplistic data handling being done externally via SQL commands. Personally I would not even consider Access unless the application were VERY simplistic.

If you are really as much a non-programmer as you claim, then you really need to decide if you really want to convert it. Will converting it provide you with what your company needs? By converting it, I assume that you will either contract it out or do it yourself. And, if by yourself, then you will need to become a programmer -- is that one of your goals?

If you contract it out, then is there a difference between contracting it to an outside programmer or purchasing another functionally compatible application from an off-the-shelf vendor? Under those circumstances, do you really care what language it is written in?

There is also the question of development timeline. How business-critical is this application? And how long can the present version keep meeting your company's needs? Again dependent on the application's complexity, some conversion/development paths take longer than others.

I guess that, in summary, I'd recommend that you make some business decisions first and then see where that leads you prior to making any language decisions.

If I can be of any further service to you, please feel free to ask.

Good Luck,
JRB-Bldr
VisionQuest Consulting
Business Analyst & CIO Consulting Services
CIOServices@yahoo.com

 

[DSummZZZ]

Well, there's not many database languages to choose from any more, and none that I know of that are any 'easier' to program in than Foxpro. Since you already have the code base made, you may want to consider converting to Visual Foxpro. It would be more of a straight across conversion than trying to translate the Fox code into another language. So my recommendation is to try to learn VFP. Look at the Fox DOS code and apply it to VFP. A lot of older procedure based code will run with no conversion. You will have to work a little harder if you start converting generated reports and screens. Start by going here:

http://www.free-ed.net/fr03/lfc/030101/129/

The other option is to bite the bullet and hire someone to do the conversion for you. Or at least help you with the conversion. It will probably pay off in the long run.
Dave S.