Migrating Clipper 5.2e to Harbour-Project Compiler 1

[tioconejo]

A. Gentlemen:

Can someone tell me how to migrate from Clipper 5.2e

to Harbour-Project compiler.

I am using AAmouse.

B. Does Harbour-Project have graphic images support as

far as filing in dbv type fields, displaying the

saved images ?

C. Does warplink (Wl32) link Harbour-Project obj's.

D. Minimum requirements to migrate. Thanks.

E. I have asked Harbour-Project Compiler people for

help but help available is very scarce.

Thanks

tioconejo

 

[rob444]

Do a keyword search on that in this forum.

Rob.

 

[rob444]

In thread288-889681 you've asked the same question.
Your primary goal should be to setup the harbour compiler and the appropiate c-compiler correctly.
It is important to set the "environment" correctly.
On the harbour website you can find examples on how to set it up correctly.

If you have that done, you can start compiling your clipper applications.
Along the way you will find some problems and there solutions, reading the documentation of the harbour compiler.
It may take some trial and error but it will be rewarding.

Good luck,
Rob.

 

[TonHu]

If additional advice is considered, please use xHarbour (from

http://www.xharbour.org),

for better performance and more modern/mature OOP features.

HTH
TonHu

 

[tioconejo]

Rob444:

A. Thanks for post, but it is two different questions.

B. xHarbour.com supports two opsys; windows and Linux.

c. Was trying to do MSdos Graphic or purely Harbour for

MS Dos.

Thanks.

Javier De La Rosa Perigault

 

[TonHu]

Answers to the original post:
A) As Rob444 told before, get the environment ready, and just compile away, (x)Harbour is nearly Clipper compatible.
I can't say anything about AAMouse, as I've never seen this lib, and don't know what it provides.
Main points of concern:
- Free version:Get the environment running properly (BCC is easy, but not fully free, OpenWatcom is fully free, but not completely implemented for all 'separate' modules AFAIK)
- Commercial version: Getting the environment right is as easy as running the setup.
- The main module needs to have a FUNCTION MAIN(...), I wrapped it in #IfDef __HARBOUR__ to be able to compile in Clipper without hassle.
- A Make script, (RMake is not usable because of long filenames :-( ), can be generated with free HBMake, or xBuild(W) for the commercial version.

B) The DBV fileformat is not natively supported by (x)Harbour, but the DBFCDX/DBFFPT (FoxPRO) RDD combination does allow for binary content in memo fields, AFAIK.

C) If WarpLink can create proper Windows 32 bit .EXE's then yes. The special '32 bit features' of WarpLink are not needed any longer as (x)Harbour generates real 32 bit apps, that can use all available memory for code & data(vars). No more DGROUP trouble!

D) Any 32 bit Windows version, Linux in several distro's, OS/2 Warp, MS-DOS (16 bits only, using DOS MingW compiler), an experimental Apple Mac version, and there are plans for Pocket-PC, .NET and 64 bit versions, so....
And ofcourse the hardware required by the OS ;-) (More is better, as usual)

E) Professional support is available from xharbour.com if you buy a support-contract, usually the (nntp://)news.xharbour.org NG is Ok, but 'newbies' are expected to dig some dirt on their own, I found out myself :-]

HTH
TonHu