We're using an utility who checks differences between FXP from different
releases of a VFP software, and it uses a simple file compare logic. We
cannot base that on "data and time modified" because these are unreliable,
expecially after another utility recompiles all of the files.
This morning we started noticing that the comparison found differences in
all of the FXP even if we modified only a few, and the reason is that the
71st byte is always different from the past releases. It looks like
something has changed in the output of the "compile xxx nodebug" command,
starting from yesterday or today.
Has anyone else had an issue as this? What could have triggered this
situation?
And, BTW, who knows where I can find info on the FXP file structure, of
about the 71st byte of FXP's?
--
Microsoft News