I am working with what is supposed to be SBT Vision Point. Which is supposed to be written in VFP 6. However, it will not run in VFP 6. Is there a way to tell from the header of the exe which version it was created in?
Wes Wilson, President ERW Custom Programming, Inc. Crescent Lake Plaza 5459 Elizabeth Lake Rd. Waterford, MI 48327 (248) 683-4182 LinkedIn Profile www.erw.com weswilson@erw.com
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
Wes Wilson wrote on 2016-05-10:
I am working with what is supposed to be SBT Vision Point. Which is supposed to be written in VFP 6. However, it will not run in VFP 6. Is there a way to tell from the header of the exe which version it was created in?
Wes Wilson, President ERW Custom Programming, Inc. Crescent Lake Plaza 5459 Elizabeth Lake Rd. Waterford, MI 48327 (248) 683-4182 LinkedIn Profile www.erw.com weswilson@erw.com
Wes,
Not that I know of. Since it is an EXE, you can use the Process Monitor tool from SysInternals to see what runtime files it attempts to open.
https://technet.microsoft.com/en-us/sysinternals/processmonitor
Tracy Pearson PowerChurch Software
On Tue, May 10, 2016 at 2:51 PM, Wes Wilson erwweswilson@yahoo.com wrote:
I am working with what is supposed to be SBT Vision Point. Which is supposed to be written in VFP 6. However, it will not run in VFP 6.
What error are you getting, Wes?
I've had problems getting VFP6 to run in more recent versions of Windows, due to some missing "common files."
Which OS are you using?
Is there a way to tell from the header of the exe which version it was created in?
There must be something, as the loader knows what runtime files to look for, but I don't know the answer to that.
Is there a way to tell from the header of the exe which version it was created in?
Yes and no - probably no with VFP executables as you'll just get references to the MS Visual C++ libs.
Try uploading your EXE into this: http://mark0.net/onlinetrid.aspx
Or download TrID from that site and try it locally. You could also use Dependency Walker but on testing here it again just lists all the Windows DLLs that the EXE imports.
http://www.dependencywalker.com/
Or you could try this utility from the Fox Wiki:
http://fox.wikis.com/wc.dll?Wiki~IdentifyFoxProVersionFromEXE
On Thu, May 12, 2016 at 9:27 AM, Alan Bourke alanpbourke@fastmail.fm wrote:
Is there a way to tell from the header of the exe which version it was created in?
Yes and no - probably no with VFP executables as you'll just get references to the MS Visual C++ libs.
Try uploading your EXE into this: http://mark0.net/onlinetrid.aspx
Or download TrID from that site and try it locally. You could also use Dependency Walker but on testing here it again just lists all the Windows DLLs that the EXE imports.
http://www.dependencywalker.com/
-- Alan Bourke alanpbourke (at) fastmail (dot) fm
[excessive quoting removed by server]
-
Alan Bourke -
Ted Roche -
Tracy Pearson -
Wes Wilson