Replication history does not log already up-to-date databases

I have an annoying issue and desperately looking for a solution…

I want to retrieve the date of the last replication of local replicas to make sure users’ local replicas are up-to-date with a given server.

The PROBLEM is that if a local replica is already up-to-date Notes will NOT log the attempted replication event in the history… which creates a problem: how would i tell the difference between an already up-to-date replica (that was replicated a month ago for example which is the displayed date in the history) and one that hasn’t been replicated recently and also has an old date in history?

The Notes help states that the Asterix (*) that is found in the replication history means that the db is up-to-date… however this is not true… you can find db’s that surely are NOT up-to-date but still their repl history displays the Asterix.

I have written code with Notes C API and LotusScript… and have yet to find a way that logs attempts to replicate already up-to-date local replicas…

ANY help with this would be much appreciated…