Quote from Tums:
so far they have narrowed down the problem to a group of users who shared (ie. duplicated) a database. And that the seed database was corrupted before it was distributed.
Stay tuned...
Quote from Tums:
so far they have narrowed down the problem to a group of users who shared (ie. duplicated) a database. And that the seed database was corrupted before it was distributed.
Stay tuned...
If you did not duplicate ProfLogic's database... then there is definitely problem with the database.Quote from Vienna:
I know this now the official MC story, but I don't believe it's true:
I had data holes appear one week where the previous week there were none. MC said that the people that experience holes had shared the same databases so had the exact same holes.
Not true in my case. I guess the randomly appearing holes in my data COULD have been caused by MC database corruption, but it does not sound too plausible.
I hope however that I am wrong, then I would have hope that this expensive annoyance ends soon...
Quote from Tums:
If you did not duplicate ProfLogic's database... then there is definitely problem with the database.
