Re: Conversion of Foxpro 2 Source to Latest Version of Foxpro or V
From: Dan Freeman (spam_at_microsoft.com)
Date: 01/04/05
- Next message: Ook: "Re: Corrupted method code"
- Previous message: Ook: "Re: How to Put a Array in a Report ?"
- In reply to: Jeff Quibell: "Re: Conversion of Foxpro 2 Source to Latest Version of Foxpro or V"
- Next in thread: TonySper: "Re: Conversion of Foxpro 2 Source to Latest Version of Foxpro or V"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 4 Jan 2005 09:09:05 -0800
You're going to find that at least SOME things are going to need re-writing
anyway. Some things just flat-out work differently in DOS and Windows.
(Printing springs to mind. <g>) Likewise, some coding techniques used in DOS
apps (printing springs to mind <g>) work differently if at all in Windows.
It's a simple fact of life. Some code techniques (such as @....GET) are
deprecated.
Microsoft *says* your 2.x code will run unmodified in VFP, and it may. Then
again, it may not. We're talking about vastly different programming
environments with vastly different expectations.
Dan
Jeff Quibell wrote:
> 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.
- Next message: Ook: "Re: Corrupted method code"
- Previous message: Ook: "Re: How to Put a Array in a Report ?"
- In reply to: Jeff Quibell: "Re: Conversion of Foxpro 2 Source to Latest Version of Foxpro or V"
- Next in thread: TonySper: "Re: Conversion of Foxpro 2 Source to Latest Version of Foxpro or V"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|