Rob Kennedy wrote on Tue, 01 Nov 2005 10:58:12 -0600:
> Not all programs have dates there because not all programs have
> resource sections.
This would work for any program it was included in because using the
ExeStamp unit causes an entry to be added to this table. I don't know of a
way to compile a Delphi something or other that doesn't include this
table, but I would gladly be corrected.
A null program contains this table and has 4 timestamps. The table
directly corresponds to what units are used, explicitly and implicitly.
SysInit and System always show up there, along with an entry for the
program itself.
program NullProgram;
begin
// null program
end.
> If Rainer wanted the compilation date of an arbitrary program, your
> method wouldn't work. But since he wants the date of his own program,
> it will be good.
Unless it happened to be an arbitrary _Delphi_ program, then DatedExe
would work. <hehe />
If one happened to be maintaining a large set of programs and DLLs in a
system, GetExeTimeStamp can be used to track the compilation dates of all
modules. The function can be passed the handle of a linked DLL as well as
the handle of the executable, so you can get the dates of libraries
currently running as part of your application (the Borland-compiled ones
anyway).
- Todd
_______________________________________________
Delphi mailing list -> [email protected]
http://www.elists.org/mailman/listinfo/delphi
