Database last modified date in the future!

pts.
Tags:
Lotus Domino
LotusScript
I have an interesting problem I hope someone can help with. I was testing/developing a view with date based calculations and decided to change my computer system date into the future to test the functionality. During this period I updated a few documents in the database I was testing and then later reset my system date back to present. However now the "Last modified" date is stuck at this future date. Also, worse, every document I update on this database shows a last modified date of this future date. Every other date function seems to pick up the current system date ok. The database in question is a local replica. The server copy shows a correct last modified date thankfully. I have checked other local replicas on my PC and only this one database appears to be affected. Question: is there any way to fix this date? or do I have to wait until the date actually comes around before it begins to update correctly?!

Answer Wiki

Thanks. We'll let you know when a new response is added.

In my experience, testing date issues in this way is a bad thing. I would try deleting replication history and trying to replicate again. However, you may need to delete the local replica. You said the the server replica was working correctly, so this shouldn’t be a problem.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Deadleaves
    I agree, in hindsight a really dumb thing to do! Oh well, we live and learn ... I have already tried deleting replication history but no change. The date in question is the one shown on database properties info tab. Also agree that most likely solution is to delete replica and recreate however, small problem. Server is in another country and database is approx 2Gb! The date is currently showing to 27 April 2006 so I figure I should go on holiday for 3 weeks and don't touch the database until then!
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following