Re: Conversion of Foxpro 2 Source to Latest Version of Foxpro or V
From: TonySper (tsperduti_at_bellsouth.net)
Date: 01/05/05
- Next message: Jim: "Combo and Exit Routine"
- Previous message: rajani: "ReadOnly property"
- In reply to: Jeff Quibell: "Re: Conversion of Foxpro 2 Source to Latest Version of Foxpro or V"
- Next in thread: Muchiri: "RE: Conversion of Foxpro 2 Source to Latest Version of Foxpro or VB.Ne"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 4 Jan 2005 19:10:28 -0500
Jeff,
You can go to VFP6 without using VFP3. VFP6 is just an enhancement of
3 and then VFP8 is again another enhancement. You should be able to go
right to VFP8 but watch out for the themes problem that I ran into
with VFP8. If you need further help just email me at
tsperduti@bellsouth.net
Tony
"Jeff Quibell" <Jeff Quibell@discussions.microsoft.com> wrote in
message news:9247BF51-B2CC-4DCE-AED6-3B2F0D94D204@microsoft.com...
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?
>
>
>
- Next message: Jim: "Combo and Exit Routine"
- Previous message: rajani: "ReadOnly property"
- In reply to: Jeff Quibell: "Re: Conversion of Foxpro 2 Source to Latest Version of Foxpro or V"
- Next in thread: Muchiri: "RE: Conversion of Foxpro 2 Source to Latest Version of Foxpro or VB.Ne"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
