Clipper conversion 2

[Imagyne]

Hi everyone..

I have some experience in MS Access, I can pretty much get it to do what I need it to do.... but it isn't pretty Anyway, I have a very old Clipper application (& corresponding .dbf/.ntx files) that is is way beyond it's use limits in todays environment. So I though I would try and update it heh..

After talking with the Original programer, who not only doesn't have the source code, but doesn't even remember clipper anymore, I decided to give it a try. I was able to decompile the .exe using Rescue5 with 2 passes. There are about 5 orginal .src or .udf files that have a line or 2 of code that ended up as garbage, but that's mostly for the screen draws.

Anyway, I have visual foxpro, what I don't have is the knowledge to actually convert/migrate this info, and actually use it... Soo that's why I'm here, hoping to gleen alot of info that will enable me to either import into foxpro, or any other app that would transform this old crusty app into a windows program that I could work with.

If anyone has any advice or info I would greatly appreciate it!

Thanks
Ken
P.S.
I did see a FAQ, however, the link listed no longer exists.

 

[JCreamerII]

Imagyne,

You probably won't get a better response here than you did on DB FORMS. Your request for help is overly broad and the conversion can be a bear and a lot of work. Most of the Clipper programmers that regularly pop by to view and respond don't like feeling they are being used without the requestor bringing most of the work to the table. If you need to get pointed in a specific direction or have a question to get answered generally you can get all the help you need.

Jim C.

 

[Imagyne]

Totally understand, and didn't realize it. I am just so in the dark on this. I apologize. I've been researching Xbase++ as well, So...
After decompile I have several .src & .udf files
Am I on the right track if I rename them to .prg files, do xpp {filename} to create object files.

Assuming that they all can be created, (there are about 5 that have errors) would a compile then be the way to go?

Again sorry for the trouble..

Ken

 

[JCreamerII]

Ken,

There is a lot going on with this type of conversion. First the (5) that have errors what do they do within the full program, maybe essential or not. What kind of shape are they in if you browse them. You could try to compile the individual PRG's to see if each can be compiled then if you get them all compiled you would have to link them into an EXE. If you take it one prg at a time it may be easier to get thru. I personnally would go for an incremental approach, get it working piece by piece.

Jim C.

 

[Imagyne]

Jim,

They browse fine and in all but 1, they have small errors that keep them from being created as .obj files... I think common syntx errors that I have to change where the Clipper code and the Xbase code don't quit match. The "1", has 2 lines of code that turned out to be jibberish, although it has to do with a screen draw.

I will do as you suggest and work the good .obj converts into exe's and try and find the correct syntax for the ones that require it. Not sure what to do with the other.

I let you know what happens.

Thanks for your help!!!!!
Ken

 

[JCreamerII]

Imagyne,

The screen draw may be calling an external lib to paint the elements on the screen. I use some with my app and they do the graphics that showup on the screens.

The other thing to think about is creating a number of small apps that would make up the whole of what the old program does. But that depends on what & how you use the old app & the how it functions.

Comment out the lines that give you a problem and compile it and run it in a test environment and eval what happens.
If you go that route you can test it piece by piece and then fold it into a new executable.

Jim C.

 

[LyndonOHRC]

IMHO,

I think you would be far better off designing a new system from scratch in whatever design environment you could get up to speed on and meet your timeline.

Even if you had clean clipper source the procedural nature of a DOS application is a poor direct conversion candidate to an OOP design.

In my case I started developing a replacement application in Coldfusion over the course of time. I started by designing an output system that offered all of our reports by connecting to the dbase data that was still being maintained in the legacy application.

Once an application had all of its output requirements proven, I could then start designing my input requirements and slowly move off of the legacy application.

Hope this helps....
Lyndon

 

[hag99]

All interesting but I have found the easiest conversion was to keep in 16 bit (I've tested in MS Vista) and it runs fine. See fivewin at fivetech for a windows interface and clipper functions. 17 years and the program works just fine. see

http://www.upyourcashflow.com

 

[jrumbaug]

Here's my 2 cents. I'm one of those dreaded part-time programers. In my office we use my 17 year old Clipper app on an XP network. I have ALMOST finished a 3 year re-write in Visual Foxpro. I now like FoxPro, but sometime wonder if I would have been better off to use Access. If you are going to stay with DBF files, I vote for Foxpro. If you are going to migrate to SQL data, you may stay with Access for a front end since you are already familiar with it. I found 90 percent or more of my code has been re-written. There were only a few routine that I could keep. I wish you luck. If you have a specific question, please start a new thread and I'll try to help

Jim Rumbaugh

 

[Imagyne]

Thanks to everyone! Many good things to think about, which is leading me to write a front end in Access and use the existing dbf files. Thanks again for all the pointers and suggestions, and again I'm sorry for originally comming as trying to get something for nothing.

*Smiles*
Ken

 

[DSummZZZ]

If you have specific questions or scenarios, be sure and take a look at the Tek-Tips Foxpro forums. There are some very good threads and posters there:

Microsoft: FoxPro (old versions 1 to 2.6)
Microsoft: VFP - Automation, Mail & 3rd Party Svcs
Microsoft: VFP - Databases, SQL&VFP, and Reports
Microsoft: VFP - Forms, Classes and Controls
Microsoft: VFP - Web Related Issues
Microsoft: VFP -General Coding Issues

-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm