Thanks Jos

Using this approach it looks like they are all version 6

Now I know what version to send out

Many Thanks




>Mark, I just did a bit more digging and this string will be within the first 10kb of a VFP6/7 exe and within 13kb of a VFP5 exe (or at least thats what I find with my apps). So you only need to read in the first, say, 20kb of the exe file.
>
>>Thanks Jos
>>
>>>Hi Mark, if you look in the exe file itself using LLFF you will be able to search for the string "VisualFoxproRuntime" which is then followed by a number which indicates the runtime version either 6 or 7 or whatever. The string will appear very near the top of the exe file.
>>>
>>>>Thanks Jols
>>>>
>>>>
>>>>These files were built without the build option to store version information.
>>>>I have tried looking at them with a hex editor but can not spot the version information.
>>>>
>>>>I tried to narrow it down by running them from the command line but they all ran.
>>>>
>>>>Version 6 seem to run version 7 executables quite happily unless a new command is used, so it is not possible to test in this way.
>>>>
>>>>The executables are either in version 6 or version 7 and I can not establish which it is :(
>>>>
>>>>
>>>>
>>>>>Mark,
>>>>
>>>>>
>>>>>Check www.news2news.com for an API that will return file info.
>>>>>
>>>>>Update: I see in the help that AGetFileVersion() will only return info if the file has "Windows version resources" information. AGetFileVersion() works for all VFP7 exe's that I have tried it on under W98 to WXP. What files does it not return info from?
>>>>>
>>>>>>I have several executables. I want to determine which VFP version each executable has been compiled in.
>>>>>>
>>>>>>These executables return nothing when AGETFILEVERSION(aFile,'myexe.exe') is run on them.
>>>>>>
>>>>>>
>>>>>>Many Thanks