>I have noticed a few times now (enough to think I see a pattern) that VFP9 can appear to "hang" if a graphic is missing.
>
>What appears to happen is that if a button or other control has a graphic that is not local, VFP9 appears to go off and search through the entire PATH statement looking for it.
>
>This seems reasonable and is not normally an issue as the minute you see the grey box with a cross you know a graphic is missing and can sort it out.
>
>However some of my control are optional, either at application level or as part of a localisation so it can occur that a missing graphic is not even going to be visible, however VFP9 will still search for it. If the PATH includes network folder the search can take a few seconds and the application appears to hang.
>
>So to my questions;
>
>1. Am I correct in my conclusion?
>2. Is there anyway to prevent this search happening?
>3. Can anyone think of a way to validate missing graphics, without rewriting every control?
>4. Can anyone advise the search hierachy? I assume within .EXE first and then through PATH setting? if so would it also check unnamed subfolders? IE. if in my PATH statment I include c:\myApp\Data\ will it search just the \Data folder or will it also check sub folders of the \Data folder even though they are not expicitly mentioned in the PATH statement?
>
>
>Gary.
Hi,

I dont have that experience, if (by mistake) an image is assigned which is not in the search-path VFP will not hang, it will simply show no image, a cross, and will go on.
I believe there must be an other reason the application hangs, could you specify the code when this is happening.
Maybe you make a small form with an image and create a procedure pointing to a non existing image?

Regards,

Koen