My company operates a series of VFP6 runtime databases successfully in the Windows XP environment.
We currenly have one PC loaded with Windows Vista. When the runtime setup is run it does not install the runtime files onto the Vista PC.
Can VFP6 work in the Windows Vista environment
How can this problem be overcome
Many thanks in anticipation.
>> We currenly have one PC loaded with Windows Vista. When the runtime setup is run it does not install the runtime files onto the Vista PC.
Vista has introduced lots of new "security" so one issue may simply be that you don't have rights to install - I think you have to logged in as a System Adminsitrator and maybe eve do something else to be able to install Vista. (This is just one of many reasons why I won't let it anywhere near any machine of ours!)
See the January Newsletter from Milind Lele at
http://msdn2.microsoft.com/en-us/vfoxpro/bb264582.aspx
Microsoft are not even testing anything before VFP 8.0 for Vista - so you will be on your own unless you start thinking about the upgrade to VFP 9.0 REAL soon.
One word of advice, when you get VFP 9.0, spend a few minutes reading the "What's New" section in the help file- there are some significant changes from VFP 6.0 - especially to the SQL Engine.
You might also consider investing a few pennies in this book too: http://www.hentzenwerke.com/catalog/wnvfp9.htm
Hi Derek.
Although it is correct your decision of buying VFP9, I don't accept that an VFP6 application doesn't work in Vista.
VFP6 is extremely simple and standard in its windows operation.
Please tell to the administrator that proves this advice, extracted of the forum of VB6:
Yes CDFAUX but besides UAC and running as Admin (generally not a good idea), some other things have changed, like the placement of My Documents and personal files, temp files, etc.
Hello Alex.
Without a doubt it is certain what you say; however that will cause problems depending on the complexity of the application: many applications VFP6 doesn't use "My Documents" neither other standard folders of Windows.
And in my opinion the point is: if I have an application VFP6 (and perhaps I don't possess the sources, or I don't have resources to convert the application to new versions), in some way I have to be able to make it work.
Saludos!
> And in my opinion the point is: if I have an application VFP6 (and perhaps I don't possess the sources, or I don't have resources to convert the application to new versions), in some way I have to be able to make it work.
I see your opinion but I don't agree. If an old app written in a very old version, to which you may not even have the source and the resources, as you say, then it cannot be ported to new operating systems.
Same (and much worse) happens wih old FPD 2.6 and FPW 2.6 apps that work in older OS and older microprocessors but will suffer a lot by being moved to today's crop of machines (dual-core) and OS (Windows Vista). Those have to stay in older hardware for the rest of their lives, or be rewrtitten/ported to take advantage of all the new stuff. That's the way it is. If the developer and/or the customer do not have the resources, then they must stay with older technology.
Conceptually I agree totally with you, but the reality indicates that we cannot always manage all the variables.
And when an old VFP app is only one of many applications that should run in a PC, don't make sense brake a hardware or S.O. upgrade.