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 9 on Windows 8
- Thread starter SBTBILL
- Start date
Olaf Doschke
Programmer
Really VFP9, or only older code moved to VFP9? Winforms don't have that behaviour of blanking out, you're first reporting such a thing for me, if you really talk about winforms and not screens. Balnking out screens built with @SAY and @GET etc. is "normal", not only on Win8. Set several things for backward compatibility, eg turn off themes by _screen.themes = .f.
Bye, Olaf.
Bye, Olaf.
- Thread starter
- #3
Dan Freeman
Programmer
I'm confused. The thread subject says Windows 8?
Olaf Doschke
Programmer
Dan, since Vista you can define a compatibility mode for any EXE.
Bye, Olaf.
Bye, Olaf.
- Thread starter
- #6
Olaf Doschke
Programmer
As you said it, it sounds like using windows xp service pack 3 mode solves the problem.
But I guess not, otherwise you wouldn't be here, would you.
Also as you said this is the (in)famous SBT Vision Point 10 software all you can do is install change compatibilty mode, you can't redevelop the software or change any sources anyway, can you?
So all we can do is a) teach you about what compatibility mode means and b) suggest installing into a virtual machine.
From my perspective and knowledge a) compatibility mode does not mean an XP system is running your software, if screen goes blank only b) installing virtual PC or Virtual Box or Hyper-V or anything alike and installing Win7 or older will help make this software run again, you can't turn off Windows themes within a software from outside and on the windows level you only can switch back some behavior to more "classic" looks. Anyway only an XP will work as an XP.
Bye, Olaf.
But I guess not, otherwise you wouldn't be here, would you.
Also as you said this is the (in)famous SBT Vision Point 10 software all you can do is install change compatibilty mode, you can't redevelop the software or change any sources anyway, can you?
So all we can do is a) teach you about what compatibility mode means and b) suggest installing into a virtual machine.
From my perspective and knowledge a) compatibility mode does not mean an XP system is running your software, if screen goes blank only b) installing virtual PC or Virtual Box or Hyper-V or anything alike and installing Win7 or older will help make this software run again, you can't turn off Windows themes within a software from outside and on the windows level you only can switch back some behavior to more "classic" looks. Anyway only an XP will work as an XP.
Bye, Olaf.
Dan Freeman
Programmer
I completely missed "compatibility mode" in the original post. Sorry. I need to slow down.
I agree with Olaf that a VM is the way to go here. I'm increasingly pushing people who need to run legacy software toward virtual machines. If software was written and tested to run on a specific platform then give it that platform, and virtual machines make it pretty easy to do exactly that.
I agree with Olaf that a VM is the way to go here. I'm increasingly pushing people who need to run legacy software toward virtual machines. If software was written and tested to run on a specific platform then give it that platform, and virtual machines make it pretty easy to do exactly that.
- Thread starter
- #9
Thanks all. I could rewrite the screens. I have the VP10 source code and am experienced in working with it. Been doing SBT since 1988. But it might take a lot of work. Haven't checked.
I'll have to look into virtual machines or maybe a better way to merge the data into Peachtree/Sage 50.
I'll have to look into virtual machines or maybe a better way to merge the data into Peachtree/Sage 50.
Dan Freeman
Programmer
You should look at virtual machines IN GENERAL, not just for this task. They're very useful.
I run VFP in various VMs every day. Among other reasons, we have old apps that we're not updating and they have *cough* specific environment requirements. We shove them into a VM and let 'em think they're still running in whatever environment they want.
I also run VFP on my Macbook in a VM. Several of them, actually. That's how I test WinXP, Win7, and Win8.x without having dedicated hardware for each. VFP thinks it's running in the real thing and I never leave the comfort of my production PC.
I run VFP in various VMs every day. Among other reasons, we have old apps that we're not updating and they have *cough* specific environment requirements. We shove them into a VM and let 'em think they're still running in whatever environment they want.
I also run VFP on my Macbook in a VM. Several of them, actually. That's how I test WinXP, Win7, and Win8.x without having dedicated hardware for each. VFP thinks it's running in the real thing and I never leave the comfort of my production PC.
- Status
Similar threads
