Re: Upgrade From 2.5 to 9.0 ???

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



It sounds like you don't really know FoxPro, is that right?

You're not very specific about what the application is.
If each desk "just" has a copy of naked FoxPro then yes, you'll need
to buy six licences. If, as everyone here is assuming (& I imagine
this is probably the case) what you've got is an *application*
written in FoxPro 2.5 then no, you *don't* need more than one
licence, and in fact you only need *that* for development.

To upgrade you'll really need to do a major upgrade.

Data won't really be a problem. You could leave it the way it is,
though you might want to convert to using database tables rather than
free ones, but you could leave it. It's not a big job to incorporate
them into the database(s), and gives you some benefits.

Converting the code actually isn't difficult, just tedious. The
automatic converter (do they still ship it?), produces rubbish.
However, it's rubbish that works, after a fashion. I seem to
remember that what we did was to use the convertor to get the screens
into some kind of VFP, then make up new screens, cut and paste the
old screen elements into it, then cut'n'paste the code into the
correct events/methods, and got it working. Then we set about making
it into good VFP code.

You'll then want to change things to use the nifty features that
exist in VFP9.

I'd suggest what you do is find a way to run what you've got without
changing it (try the Citrix &tc, routes being suggested elsewhere) so
that you're flavour of the month with the client and they've got
something running straight away. Then point out to them the
benefits of a proper solution (ie upgrading to VFP9), and so secure
another chunk of work.

Have fun.

.



Relevant Pages

  • Re: Conversion of Foxpro 2 Source to Latest Version of Foxpro or V
    ... this is a link to an older white paper on converting from FoxPro 2.x ... > were on FPW screens, ... The reports also set up the reports ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Problems saving effects entire app
    ... optimize VFP's internal usage of memory. ... Microsoft FoxPro Technical Support ... Did your users upgrade the hardware with the "new" ... I'm planning to upgrade the app to version 8.0. ...
    (microsoft.public.fox.vfp.dbc)
  • Re: conversion from dos version of foxpro2.6 to any visual foxpro version
    ... Look at Chuck Urwiler's FoxPro Advisor ... this is a link to an older white paper on converting from FoxPro 2.x ... form and report changes due to the>non-proportional differences for field ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Migration Foxpro 2.5 to .NET
    ... You can simply move the code from FoxPro 2.x into VFP. ... this is a link to an older white paper on converting from FoxPro 2.x ... multiple users due to the users needs. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Upgrade from FPW/DOS 2.6 to VFP6.0
    ... them but they regularly crop up here in response to old version requests. ... By the way, when looking at the qualifying software for the Upgrade version of VFP6.0, it says: "Professional Upgrade - This Upgrade can be installed if you currently have FoxPro 2.5 or later for the PC or Visual FoxPro 3.0 or later for PC or Mac." ...
    (microsoft.public.fox.programmer.exchange)