>It sounds like you've used image files from the VFP directory
Indeed, and normally that would make use of HOME(). If you use FFC, there are quite a lot references making use of HOME() to reference files in the VFP directory. Then it wouldn't matter where VFP is installed, as HOME() would always point to it. Also within classes and objects of the VFP Directory paths are stored relative and that also wouldn't matter.
It's not the way picture references work, though. Within a scx or vcx class the picture property does not make use of expressions like HOME(), you have relative paths stored in there. So that wouldn't be a problem, either. But using the grpahics in your own objects within files you have in your project folder, you neither have relative paths nor HOME() expressions, but absolute paths in your picture properties.
That's another reason why using foxpro classes and graphics is to be avoided to keep all your project self contained. Even if you copy them inside your root project folder you would get awkward references from there to HOME() folder parent classes etc and that's also no healthy project state.
Dan is right, just specifying a graphic in it's new location, then save. That mends this case. Other classes/objects will also find the new location, too, but only during the current VFP session, if VFP finds some file in a new location it has memorized by your earlier adjustment, that'll mean you get no dialog asking for redirection, but then there is no change to the vcx/scx and so it still has a wrong reference inside that's just auto-corrected for the current session. VFP doesn't memorize path changes forever. Next time you start vfp and open up some other vcx first that hasn't been changed, that'll prompt for finding a graphic or parent libraries, etc. If you want to tidy up the whole project, you should use some utility like hackscx to adjust all paths.
And no, I wouldn't blame MS. The FFC classes are so old, they are out of support and test. Also you have a choice where to install VFP, you could simply reinstall it in the old /program files/ folder, just create it. You'll have problems with a VFP installation into protected system folders anyway. Many prgs and other stuff within HOME() is just compiled or indexed or generated at first use (eg first time using Code References generates some DBFs) and all that isn't written in /program files(x86) but in your user profile because of redirection of write operations.
Bye, Olaf.
