Try
-database compact/repair
-renaming your report by appending OLD to its name, then bring in the report from the sample db you created. I'm thinking the original report might be corrupted, hence the compact/repair suggestion. The sample db report might be OK, which could explain why it works for others.
There are a few conditions that might provide clues:
Is this the only report that does this (assuming you have others to work with)?
Does it freeze at the header? Detail section? Which view, report or print? OK in design view?
The rest of Access is OK?
I wouldn't monkey around with Office just yet.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.