One side effect of the Check In Command beeing configured to save working file timestamp
is that the check in date will not be seen in the member history but the working file timestamp.
This can falsify the picture of the development process as the timestamps in member histories
do not necessaryly reflect the time a revisions was checked in resp. available for other users,
but when it was saved.
The only reliable information of a time range can then be gained if the revision number is
between 2 checkpoints.
Is it possible to find out the check in date of a specific member revision
independent of which setting of "Save Working File Timestamp" was active at checkin time?
(Maybe the transaction time is also stored in the Integrity database)