I don't recommend changing the system date like this. Modify your design so that you can specify a date and then a script uses the date you've specified to pull up your report.
While I've never got a crash from doing so, the system clock is used in a lot of different areas so a change in it's data can affect many areas of your computer and many different applications. I've found, for example, when doing a quick test of a feature in Filemaker where I needed to confirm that a FileMaker feature was working correctly, that this forum will kick you out if you have a past date set in your system clock.
Have you used recover to check your file for issues? Reverting to a back up after a crash is good practice as it avoids issues created by the crash, but if you already have some hidden file damage that is causing your crash, it will still be with you and running a recover on the file may reveal such an issue.
Things to keep in mind about Recover:
While Recover almost always detects and fully corrects any problems with your file...
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.