I know the actual install of VFP v9 in Win10 Pro x64 has been accomplished successfully by others, but my question is how well will it display with PRG/FXP files created in FPD v2.6 without changing any code? It seems they will "not look right," but I haven't found a specific explanation of what that means. Most say the code should or must be re-compiled in VFP, but my main PRG contains 800k lines, so that's not a feasible solution for me. If someone could describe and/or show pix of how this might look I'd appreciate it. I'm not going to install VFP unless there's a good change I can make it work properly without major coding changes. BTW I don't know anything about VFP coding and at my age I'm not keen on learning a new language. My strategy in the past has been to simply have a dedicated x86 machine connected to my main machine, which currently runs Win10 Pro x64.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VFP v9 in Win10 Pro x64
- Thread starter BobDavis
- Start date
Chris Miller
Programmer
VFPs compatibilty with legacy code is quite good.
VFP has let Windows themes take some control, that's set off by _SCREEN.Themes=.F. or the more cryptic SYS(2700,0). It's necessary as the themes support causes some strange side effects like controls of screens only becoming visible when hovering over them with the mouse.
As your origin is DOS, though, that's still a step towards windows, so you'd still run this in a DOS replacement.
compiling 800 lines isn't that big problem, I think you fear compile errors and how to fix them.
If you don't want to buy for trying, you could take the latest SP2 of VFP9, use 7zip to extract vfp9.exe from it and the vfp and c runtimes, then start vfp9 with a lot of things missing, but able to use the command window to COMPILE some.prg and see what it gives.
Chriss
VFP has let Windows themes take some control, that's set off by _SCREEN.Themes=.F. or the more cryptic SYS(2700,0). It's necessary as the themes support causes some strange side effects like controls of screens only becoming visible when hovering over them with the mouse.
As your origin is DOS, though, that's still a step towards windows, so you'd still run this in a DOS replacement.
compiling 800 lines isn't that big problem, I think you fear compile errors and how to fix them.
If you don't want to buy for trying, you could take the latest SP2 of VFP9, use 7zip to extract vfp9.exe from it and the vfp and c runtimes, then start vfp9 with a lot of things missing, but able to use the command window to COMPILE some.prg and see what it gives.
Chriss
Gerrit Broekhuis
Programmer
Chriss,
I think it’s 800K lines the OP is talkink about.
Regards, Gerrit
I think it’s 800K lines the OP is talkink about.
Regards, Gerrit
Chris Miller
Programmer
k.
M fault to overlook this. Still projects with a million lines do compile, too. I see that you would not expect that to compile free of any errors due to language changes, just because the code did compile to FXPs already, but I'd still also consider it worth trying to have object code runnable with the more modern VFP9 runtime.
Chriss
M fault to overlook this. Still projects with a million lines do compile, too. I see that you would not expect that to compile free of any errors due to language changes, just because the code did compile to FXPs already, but I'd still also consider it worth trying to have object code runnable with the more modern VFP9 runtime.
Chriss
- Status
