INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

Clipper code migrates easily to 32bit Alaska xBase++

Clipper code migrates easily to 32bit Alaska xBase++

(OP)
Forgive me if this topic has been covered already.  

I am an old Clipper guy from the S'87 days (and before).  Own S/N 1299 of Clipper.  It has served me well as a consultant and software developer.  Alas, Microsoft has been pushing 64 bit O/S and things got dicey.

Have been using Alaska xBase++ for several years and I will say that for me it has been a splendid migration path for old Clipper programs.  Some code compiled w/o change.  Most required some minor tweaking (such as every base program has to start with a Main() function.

Alaska xBase++ has the added benefit of creating 32 bit apps that will run in a 64 bit environment.  

Is worth checking out as more and more equipment is being implemented w/64 bit O/S.

Disclaimer:  I have NO affiliation with, nor any monetary interest in Alaska.  It is simply a good migration path from Clipper.  A bit costly - but perhaps worth it if you have significant investment in Clipper source code.

RE: Clipper code migrates easily to 32bit Alaska xBase++

I've used Alaska xBase++ for a while too. The migration was not painless and some things just never got ported across, but it is reliable and reasonably quick.

I prefer VFP now, but I'm actually working on a C# conversion of a Clipper->xBase++ project as we speak!

M

Regards

Griff
Keep Smileing

There are 10 kinds of people in the world, those who understand binary and those who don't.

RE: Clipper code migrates easily to 32bit Alaska xBase++

I've switched to Harbour/xHarbour somewhere over 10 years ago, just to get descent (then 32 bit, now even 64 bit) performance out of my old code. And then I stopped using/supporting Clipper/xBase coding entirely...

Like Griff, new code is in C# or Java, and IMHO old code/applications usually needs a giant redesign anyway, so doing it, properly designed, in an Object Oriented environment is the best way to go.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close