Re: Conversion of Foxpro 2 Source to Latest Version of Foxpro or V

From: Lee Mitchell (Leemi_at_online.microsoft.com)
Date: 01/04/05 

Date: Tue, 04 Jan 2005 16:05:20 GMT

Hi Jeff:

You can take the FoxPro 2.x code directly to VFP 8.0 or VFP 9.0.

Here are some conversion resources that may prove useful:

Chuck Urwiler's FoxPro Advisor article at:
http://foxproadvisor.com/doc/05239

Also, this is a link to an older white paper on converting from FoxPro 2.x
to VFP 5.0. While the information is a little old, much of it is still
applicable to later versions:

http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dnarfoxgen/
html/msdn_movfox.asp

While you can convert the code, in the long run the client may save money
by simply rewriting the code in VFP 8.0 or 9.0. If the code base needs
constant updates, the cost of updating the old code can be considerable.

I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
   - VFP5 Mainstream Support retired June 30th, 2003
   - VFP6 Mainstream Support retired Sept. 30th, 2003

>Tony,

>Was the progession from 2.6 to 3 to 6 important? I can acquire VPF6 and
>later, but not sure I can get 2.6 or 3 to do the initial steps. My
customer
>is not really interested in a rewrite if there is another alternative.

>Thank you!

>Jeff

"TonySper" wrote:

> Jeff,
> I have been using Dbase, FoxBASE, FP dos, FPW, VFP3, VPF6, and now
> VFP8. I have a large program out there that has over 600 users that
> was originally developed with DOS converted to FPW2.6 updated to VFP3,
> then VFP6, and now VFP8. Yes I had some problems converting them but
> nothing that could not be overcome. Little things like the lines that
> were on FPW screens, (now forms) would not convert. Kept giving me
> errors, the databases had to be updated but then the program did that
> by just asking me if I wanted to convert. The reports were the hard
> ones as I had to rewrite them. The reports also set up the reports
> with the printer that you are using and that gave me some problems. I
> had to write a program to go through the report database and remove
> all the references to the printers. The old screens give me a bad time
> once in a while when I add an object that has to be updated I have to
> remember to go into the load part of the form and add another this
> variable update line. When I converted the screens to forms I removed
> the spx files that were on the old screens and went through the
> program were it opened the screens to opening the forms. When the
> screens get converted to form it generates extra file with a 2x after
> them that I went through and removed also. The one big problem I had
> was when I went to VFP8 and when a user put the mouse over the form it
> went AWOL and then came back. Users in this group helped me out and
> told me it was the Themes. I just shut off the themes and cured that
> problem.
>
> All in all I sometimes wished that I bit the bullet and updated the
> screens instead of converting them and maybe someday I will. I am old
> fashion and hate to do new things, (still fighting OOPS), but I will
> stick with VFP as my learning curve of other programs is well below
> what I know with VFP. I know I only use about 50% of what is their but
> am happy with it as I can do most anything I want with it. Not the
> purist of programmers but get it done with the help of these good
> people on this news group.
> TonySper
>
> "Jeff Quibell" <Jeff Quibell@discussions.microsoft.com> wrote in
> message news:48D45A88-4683-4F04-B126-8DAAF2AF2DE8@microsoft.com...
> I have a client that wants a Foxpro 2 application updated to the
> latest
> version of the language or VB.Net. They have the source code. Any
> suggestions on how best to proceed?
>
>
>

Relevant Pages

  • Re: Conversion of Foxpro 2 Source to Latest Version of Foxpro or VB.Ne
    ... then VFP6, and now VFP8. ... were on FPW screens, ... The reports also set up the reports ... screens instead of converting them and maybe someday I will. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Conversion of Foxpro 2 Source to Latest Version of Foxpro or V
    ... and then VFP8 is again another enhancement. ... > were on FPW screens, ... The reports also set up the reports ... > screens instead of converting them and maybe someday I will. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Upgrade From 2.5 to 9.0 ???
    ... It sounds like you don't really know FoxPro, ... To upgrade you'll really need to do a major upgrade. ... Converting the code actually isn't difficult, ... remember that what we did was to use the convertor to get the screens ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Conversion of Foxpro 2 Source to Latest Version of Foxpro or V
    ... is not really interested in a rewrite if there is another alternative. ... > were on FPW screens, ... The reports also set up the reports ... > screens instead of converting them and maybe someday I will. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Migrating FPW2.6 application
    ... I have been using Dbase, FoxBASE, FP dos, FPW, VFP3, VPF6, and now ... then VFP6, and now VFP8. ... were on FPW screens, ... screens instead of converting them and maybe someday I will. ...
    (microsoft.public.fox.programmer.exchange)