Discussion Locked

MS-DOS clipper app vs Windows GUI

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Gang, I am inn a real bind here. Can anyone pass on any links, articles, info on whether or not to convert an Ms-DOS Clipper program into Windows.

My company believes they can use their DOS clipper data gathering system for many more years sinceit works under the cmd in Windows XP.

Being a software developer for the company, my team of 4 already created a GUI reporter for this data gathering system, but the problem is DOS chews up the resources. We have been trying to persuade the uppermanagement to re-write the software to a GUI app, but no one is cool with it because they say "DOS still works to why bother"

What you do all think? Any information about this topic is GREATLY appreciated.

Thanks, Art

5 replies

by stillatit

Clipper is a compilable clone of dBase. The easiest way to move it to Windows will be converting to Foxpro. Hopefully you have the source available.

Probably about 80% of the non-screen code will transfer directly, with some functions needing syntax adjustment or replacement by existing functions. (Some functions had different names in Clipper than Foxpro, and some had different syntax.) The screen code should be converted to Visual Foxpro forms, which is fairly quick. The validation subroutines for the various fields should be moved to code snippits, but can be left in one large code file as functions, and called by the form as needed.

By the way, the reason that it is a resource hog is that the I/O works by polling the keyboard (has a key been pressed?...has a key been pressed?...and so on.) It is fair to say that if you have such an app running in the background, don't plan on anything running fast in Windows, no matter how fast your computer is. Since it is a DOS single-userapplication, it NEVER gives up control voluntarily -- Windows has to snatch control away from it.

Good luck.

by estebandelatorre

Clipper is like dbaseiV, dbaseIV was like Foxpro, Foxpro for dos has move into windows, so the better way to move from clipper is to foxpro for windows, but as time goes by, there will be less upgrade posibilities without re-writing much code.
You have 2 clear possibilities
1.- Let the DOS application die, do not spend your budget in re-writing code without any new functionality. Instead buy faster machines and more and more memory.
2.- Move in silent. Each time a new function/program has to be added to the system, develop it in a windows database compatible system like foxpro or access, but never develop into DOS more.
I'm sure that your boss will agree with this last one.

This discussion is closed to new replies.