Hello. The application I work with is fairly graphic-intensive(as far as VFP apps go, anyways), and we've run into an annoying problem. If a graphic is included in the VFP executable with a specific name, and an Image's Picture property is explicitly set to a full path(outside the application's path) that happens to have the same name as the included image, the included image is used instead. Steps to recreate:


1. Create a single-form EXE
2. Add an Image object to the form
3. Add two buttons to the form
4. Code button 1 to set Image.Picture to "test.bmp" when clicked
5. Code button 2 to set Image.Picture to "c:\test.bmp" when clicked
6. Include a test.bmp in the project, and compile
7. Put a different test.bmp in c:\, and run the executable

When clicking on button 2, the bitmap inside the executable is shown instead of the bitmap residing in "c:\" This doesn't happen when running directly in the VFP IDE, but in compiled mode, is thinks it already knows what "test.bmp" is, so it uses it's included version instead of the explicit path I'm pointing to. Any ideas to get around this?

This test project(written for VFP7) is available at http://www.sensiblesoftware.com/junk/test.zip (43kb including test bmp's).