Of course I've understood your question, just trying to point out that it's no longer a concern since keeping VFP is no longer a risk and rewrite brings no additional value.
As far as I know, all clone languages (Lianja, x#, xBase++) require changing the VFP code; as soon as you change a single line of your app in a non back compat manner, it becomes a migration where you can't safely step back; and here come the risks and costs.
Thierry Nivelet
Le 14/03/2019 à 17:45, Fletcher Johnson a écrit :
Thierry,
All I know is that there have been a number of comments about various options that are similar to VFP that have come out (X# is one) where VFP code will more or less run, especially with some of the built in conversion tools.
So the question isn't whether to stay with VFP, but if there are any alternatives that will run the VFP code without significant re-writes.
Thanks,
Fletcher
Fletcher Johnson FletcherSJohnson@Yahoo.com LinkedIn.com/in/FletcherJohnson twitter.com/fletcherJ strava.com/athletes/fletcherjohnson 408-946-0960 - work 408-781-2345 - cell
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Thierry Nivelet Sent: Thursday, March 14, 2019 3:24 AM To: profox@leafe.com Subject: Re: [NF] Looking for current summary of VFP clones
Hi Fletscher,
Does your client really knows that, since 10 is the last version of Windows, VFP will work as long as Windows 10 will work, and re-write and/or migration will bring nothing but cost and risk without a single benefit (except for those who rewrite): learning, moving data to SQL if not already, rewriting, testing, retraining users, managing the transition with part of the app in VFP and part in the new system (no new app ever work overnight), etc., maybe loss of functionalities, and risk that the transition works out badly…
Seeking alternatives to FoxPro was valid until Microsoft announced that Windows 10 was the last version (in may 2015, almost 4 years ago), today it's just seeking cost and risk for no other benefit than 'doing someting new'.
VFP is incredibly reliable; some FoxInCloud clients have FoxInCloud web apps with over 50 forms (could be more), 50 concurrent users (could be more), PostgreSQL database, 8 logical servers in parallel (stateless, many-to-many relation between users and servers), running full weeks without a single error (100% availability) while reading and writing thousands of files, tables, memos, indexes and so forth. The busiest server runs 25k user requests per day, that we can estimate over 1.2 billion VFP instructions, without a single error…
Bringing additional value to the existing VFP app is probably more worthy and interesting than rewriting; eg. with FoxInCloud.
(I know I don't really answer your original question, just trying to open new pathes).
Thierry Nivelet FoxInCloud
Le 13/03/2019 à 16:45, Fletcher Johnson a écrit :
Hi all,
I was asked for a list of current options for someone who has a VFP application and wants to migrate it to a supported language, with the least amount of re-work.
I have seen many options listed, but am sure how compatible the various alternatives are. X# looks promising, but so do some of the others. And some that I thought were good options now appear to be dormant or discontinued. So I thought I would check with you fine folks to see if you know where I might find a list of current alternatives and their level of compatibility.
Thanks,
Fletcher
Fletcher Johnson
mailto:FletcherSJohnson@Yahoo.com FletcherSJohnson@Yahoo.com
http://linkedin.com/in/FletcherJohnson LinkedIn.com/in/FletcherJohnson
twitter.com/fletcherJ
https://www.strava.com/athletes/fletcherjohnson strava.com/athletes/fletcherjohnson
408-946-0960 - work
408-781-2345 - cell
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]