Hi Mike !

>Peter,
>
>I found this MSDN reference to be extremely helpful:
>
>Using the Registry

It sure is. I don't know how you guessed it, but the stuff in there is what we want eventually.

>
>Also see this thread on UT:
>
>ExtractIcon or ExtractAssociatedIcon

Well, that should cover it.

>
>And check out George Tasker's Icon Extractor - Download 13845

Thank George, and I guess Alexander for it !

>
>George's utility requires VFP 7, but note that Alexander Golovlev describes a routine that works under VFP6 in the preceding thread (see Message #656045).

VFP7 should suffice ;-))

>
>HTH,
>
>Mike

Good work Mike ! Thanks.

Peter


>
>>Possibly this was in here before :
>>
>>For each extention (EXE, WAV, DBF, PPT, etc.) there will be an Icon, which we also can define ourselves.
>>How can I retrieve that from within VFP ? I suppose it needs to read the registry.
>>
>>For each application (VFP, Excel, Outlook, IE, MyApp etc.) there will be an Icon, which we also can define ourselves.
>>How can I retrieve that from within VFP ?
>>
>>
>>Please note that both of the above are not the same.
>>Also note that I don't want to define them from within VFP; I only want to pick them up.
>>As for the applications, the API-call needs to be fed with the version of the application. Hence, Word6 has another Icon than Word8. Because my app will be putting the Icons on some Form, there has to be some differentiation between the user pointing to the physical location of e.g. Word6 versus Word8, and another API retrieving the version of that (EXE) file. Possibly, this API can retrieve the Icon from the app from this point already (hence here the registry is not needed).
>>
>>Obviously all has to be transparent opposed to the Win-OS.
>>
>>Can it be done ?
>>Thanks for any help !