If you are having a problem with the Reports Module, there are a few things you can do to help us help you fix it.
First, be as descriptive as possible, in order to fix the issue we have to be able to reproduce it (otherwise it is very difficult, if not impossible, to track down where the problem is). Tell us what browser you are using, what were you doing when you encountered the bug, and (if there is one) give us the public URL. If you do not wish to give out the public URL on the fourm, please email me at: andrew DOT nurse AT dotnetnuke DOT com.
Second, please be patient, this is a volunteer project and currently there is only one person working on it (me). I plan to start looking for people to help out soon, but until that happens it's just me. The Reports Module is something I am very focused on, but I do still need to make a living and study so sometimes those things get in the way. As an open-source project, you and the rest of the community have full access to the source code so feel free to dive in and tincker with it. If you manage to solve your problem, please tell us how so we can integrate it into the main codebase!
Thirds, ALWAYS search the forums and tracker to see if you problem has already been encountered (and possibly fixed). That way we can save everyone's time.
Finally, please use the public issue tracker at: http://support.dotnetnuke.com to report issues. Isues there that are clearly marked as relating to the "Reports Module" (I highly recommend using that exact text somewhere in your Issue Subject or Body) will be moved into the Reports Module Private Tracker and have a much better chance of being fixed)
I hope the community is getting benefit from this Module, I have worked hard to try and make it the best that I can. However, there are always bugs, new feature requess, and enhancement request and hopefully this short guide can help you get your answer fast