Encerrado

Clipper to Windows

I have a Duplicate Bridge Scoring Program written in Clipper which I want converting to a MS Windows application.

The linkage structure is slightly convoluted due to size and addressing constraints inherent in DOS based programs. These would of course be simplified in converting to a Windows based program, where in the simplest terms all the program modules would be strung together to give one executable module. The basic structure of the overall suite is:

There is a small batch program ([url removed, login to view]) which executes PAIRMENU.EXE. This is merely a list of seven executable modules chained together within. Each module is given a sequential number, and each program in the list can direct execution to another program through a DOS exit code set by ERRORLEVEL() (At start up PAIRMENU executes the first program in the parameter list - SCORER.EXE. Thereafter PAIRMENU executes the program whose sequential position in the parameter list equals the indicated exit code). None of this would be required under a Windows based program.

The seven executable modules are: [url removed, login to view]; [url removed, login to view]; [url removed, login to view]; [url removed, login to view]; [url removed, login to view]; [url removed, login to view]; UTILMENU.EXE. ( [url removed, login to view] is the one which does the bulk of the actual scoring). Probably [url removed, login to view] could be ignored since the functionality provided within this (i.e. ladder maintenance routines) is rarely used by any clubs.

Each of the above executable modules is composed of a number of object modules, each together with two object modules relating to the actual Clipper instructions (CLIPPER and EXTEND - if these are needed in the re-development process please advise).

The composition of the executable modules is:

SCORER - [url removed, login to view]; [url removed, login to view]; [url removed, login to view]

EVMENU - [url removed, login to view]; [url removed, login to view]; [url removed, login to view]; [url removed, login to view]; [url removed, login to view];

MOVEMENU - [url removed, login to view]; [url removed, login to view]; [url removed, login to view]

NAMEMENU - [url removed, login to view]; [url removed, login to view]; [url removed, login to view]

LADMENU - [url removed, login to view]; [url removed, login to view]; [url removed, login to view]

MPMENU - [url removed, login to view]; [url removed, login to view]; [url removed, login to view]

NAMEMENU - [url removed, login to view]; [url removed, login to view]; [url removed, login to view]

UTILMENU - [url removed, login to view]; [url removed, login to view]; [url removed, login to view]

As you can see there is a considerable amount of duplication within the .EXE modules particularly in relation to [url removed, login to view] and [url removed, login to view]

Within the Clipper linkage, when creating the object module, each individual .PRG program is automatically linked within the lead object module (e.g. when using the development Clipper command 'tlink evmenu', all the routines in the chain headed by [url removed, login to view] are picked up and linked together).

Habilidades: Área de trabalho do Windows

Ver mais: clipper windows, clipper prg, clipper linked list, set of pairs, prg, none given, n equals, maintenance position, clipper tlink, obj c, obj, help windows, execution, DOS, composition, clipper, chained, batch program, module windows, clipper dos, small batch, windows development, course module, command batch, program windows

Acerca do Empregador:
( 0 comentários ) Llandrindod Wells, United Kingdom

ID do Projeto: #582010

1 freelancer está ofertando em média $230 para este trabalho

mysilversir

Please contact for further discussion about work on rajatsolanki for yahoo, rajat-solanki for skype, rajatsolank007 on gmail

$230 USD in 10 dias
(0 Comentários)
0.0