Here are the steps I performed:

1. removed '<add key="InstallationDate" value="..."/>' line from web.config.
2. copied the whole original Install folder over to my web server.
3. ran a script to delete all DotNetNuke tables, views, sprocs, and functions. This left the db and its security settings in place for convenience.

When I performed these steps with Medium trust configured in web.config, the Reports module failed to install.

When I repeated the same steps but also changed the trust to Full, everything including Reports succeeded. :)

Glad I could help. While I'm still learning DNN and testing things, I don't mind reinstalling or doing other tests. Let me know if there is something else related to this issue that I can test in the future for you.

BTW, I really like the Reports module. I know it is fairly simple right now, but it is very useful. The next feature that would really help me is having some options for column width. I would like to see two things:

1. let users drag individual column widths.
2. let users click to fit all columns in their browser width.
3. let admins specify some default column width settings (such as fit-all, etc.)

If you eventually duplicate the functionality of a data grid such as Developer's Express, Infragistics or Telerik, etc. where there is group-by functionality and all the other advanced stuff, that would be really cool.

http://www.infragistics.com/Products/NetAdvantage/WebForms/GridsFeatures.aspx

As a short term solution, once I learn more about DNN, I would like to just build a reports module using the Infragistics grid (because I have a subscription to Infragistics) for my own use. Of course, that doesn't help the general DNN user. For the community, it would be really cool to have an advanced open source data grid component.

I just found these links that may interest you (or you may be beyond this point already):

• http://www.codeproject.com/cs/miscctrl/csharpgridcontrol.asp
• http://www.devage.com/DevAgeSourcePack/SourceGrid3_EN.html

Thanks for making the Reports module available!

Hi Andrew, I have just come across another issue related to the Reports module. It isn't a problem with the module, but it is a problem related to the fact that the Reports module requires codeSubDirectories to be added to web.config.

      <codeSubDirectories>
        <!-- <add directoryName="Reports" />-->
      </codeSubDirectories>

When this is done, any other ASP.NET application running in a virutal directory under the DNN web site will fail with an error that it is missing the Reports folder.

For example, I just set up Community Server in a virtual directory under my DNN web site. If I comment out the '<add directoryName="Reports" />' line shown above, I can get Community Server to run. However, if I do not comment out that line, I get an exception. I spent several hours looking at various options and I didn't find anything that worked well except to get rid of the codeSubDirectories. (For example, I tried two different web sites instead of a virtual directory, but that was satisfactory. I also tried to get DNN to run in a virtual directory along side CS, but I couldn't get that to work - seems DNN cannot create a child portal without a parent.)

BTW, if anyone know the lastest about DNN 4.3 and CS 2.1 integration, I would like to find out. All I have found is from a year ago here: http://blog.danbartels.com/archive/2005/06/28/753.aspx

Thanks