by The00Dustin (Posted Thu, 16 May 2013 09:44:06 GMT)
Fair enough. Let me know what you find out. Also, remember, it may or may not have broken when I performed the update from 6.34 to 6.42, so if you don't have the problem, something else (like a power failure or software crash) might have caused it. I actually checked the box to remove them, closed the software, opened the software, unchecked the again, and closed the software only to have it crash before it shut down. This may have been due to the fact that it was still working on the database in the background, so I performed the same procedure again without the crash. Another download will tell me whether or not that made any difference, but in the meantime, I'm wondering if there is a procedure I might need to perform manually in order to repair or finish optimizing the database.
Read Main Topic
Fair enough. Let me know what you find out. Also, remember, it may or may not have broken when I performed the update from 6.34 to 6.42, so if you don't have the problem, something else (like a power failure or software crash) might have caused it. I actually checked the box to remove them, closed the software, opened the software, unchecked the again, and closed the software only to have it crash before it shut down. This may have been due to the fact that it was still working on the database in the background, so I performed the same procedure again without the crash. Another download will tell me whether or not that made any difference, but in the meantime, I'm wondering if there is a procedure I might need to perform manually in order to repair or finish optimizing the database.
Read Main Topic