Stephen - interesting points - especially as that is probably EXACTLY What UCLA wants!!!
-K-
On 3/14/2019 1:17 PM, Stephen Russell wrote:
In all the years of writing apps have you ever had a talented user who told you what they wanted to be even close to what they ended up with?
That being said, a rewrite allows the developer to "fix" the poor decisions and tweaks to fix them. If you had that commitment from the champion why not get it off the desktop and make it contemporary to apps in the 2020 time frame? That could be cloud, web, tablet/phone, as well as PC. Those may be what the user wants in the re-write anyway.
On Thu, Mar 14, 2019 at 12:01 PM Kevin J Cully kjcully@cherokeega.com wrote:
I think this is key. You all know that I'm a huge Xojo fan, however I can't ever believe that rewriting an application for something other than a real concrete reason is a good idea. Basically if you are wondering if you should rewrite a VFP application, then the answer is "no" already. If you know you need to rewrite a VFP application, then you already know why it needs to be rewritten, by definition. (Examples: Needs cross platform. Needs 64-bit. Can't interface with 'X'. etc.)
Great post Thierry.
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Thierry Nivelet Sent: Thursday, March 14, 2019 6: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]