>>>>>Hi all,
>>>>>
>>>>>In thread # 581909, Alexander Golovlev attempted to assist me with parsing out the Windows file description contained in an EXE file using the VFP internal AGETFILEVERSION() function.
>>>>>
>>>>>Unfortunately, it only seems to work about half the time. Many EXE files, which show a Windows description in Explorer/My Computer, can't evidently be seen by the function and it returns 0 with no information in the array.
>>>>>
>>>>>These files seem to have one common "thread" (pun intended) -- they have all been created with the Wise Installer (at least, the Wise Installation Wizard comes up when I run each one separately). I have *hundreds* of these files for which I need to grab the contained description.
>>>>>
>>>>>Anybody out there know another way to get this info besides AGETFILEVERSION?
>>>>>
>>>>>TIA,
>>>>
>>>>You mean like "Microsoft Visual FoxPro Table" and so on that appears in the Windows Explorer?
>>>
>>>Hi George,
>>>
>>>Not exactly. If I select the EXE file in My Computer, right-click it and choose "Properties", I get a dialog box that lists type of file, location, size on disk, and so forth. One of those items is "Description" (ie, "Theme-Pak TP-Abstract Yellow for NetObjects Fusion" or some such). I want to extract that description text.
>>>
>>>Thanks,
>>
>>I thought so. Alexander gave you the right answer. The problem is that not all executables and DLLs store this information. Further, if memory serves, I believe that if it trys to store it, the platform it's being compiled under may come into play. When I'd compile a VFP Com server DLL under Win98, the internal information wouldn't show. Under Win2K it does.
>
>Okay, I think I understand -- but if it wasn't *stored* with the EXE, how does Win2K see it to show it to me in the dialog box?

If it's showing a description, then it is stored in the executable. Why AGETFILEVERSION() wouldn't show it in the 3rd array element, I don't know. If it's showing a "File of type", it's resolving the extension from the registry.