Is she running the report from inside Visual Studio or from the reports website ?

I have seen this happen in Visual Studio but when not when run from the reports website. I don't think that there is anyway around the issue if you are using Visual Studio (Other than deploying the report and then running that).