Programmatically stop replicator from replicating outdated database?

We are experiencing the issue with old docs created back in the database due to someone who replicates a local database with server after the expiry of deletion stubs. This is causing all the old docs to be added back into server. We could put in all kinds of reminder and alerts for the users, but they could easily ignore it.

Can we programmatically stop the replicator from replicating a database that has not been replicated after X amount of days? Just to be very clear, the replicator I meant is the replication page on client with a list of databases where scheduled replication is set.

Any ideas or advice appreciated. Thanks

Subject: nope, but…

I have been asking IBM to build in a check for this. the server should block the replication if the purge interval exceeds the last successful replication with a server. I was forced to build a routine that trigger’s off the PostOpen event and gets the last successful replication and if it exceeds 30 days it locks the user out by adding their name to the ACL with no access. It’s much more comlplex than I have explained above but you can work out the logic if you need to do something similar.