FAQ/Storing-Reports.md
... ...
@@ -35,10 +35,10 @@ Public Class CustomAdHocConfig Inherits Izenda.AdHoc.FileSystemAdHocConfig
35 35
36 36
One of the advantages of file system mode is that it allows for custom saving behavior. There are four main methods that control creating, loading, saving, and deleting reports:
37 37
38
-* ListReports
39
-* LoadReportSet
40
-* SaveReportSet
41
-* DeleteReportSet
38
+* [[ListReports|/FAQ/ListReports]]
39
+* [[LoadReportSet|/FAQ/LoadReportSet]]
40
+* [[SaveReportSet|/FAQ/SaveReportSet]]
41
+* [[DeleteReportSet|/FAQ/DeleteReportSet]]
42 42
43 43
Each of these methods may be over-ridden in order to implement custom behavior. Please see the global.asax example and the Izenda Reports API for examples. To set the default reports folder path that Izenda Reports should use, you must first create a folder in the file system and then ensure that the *NETWORK SERVICE* machine account has read and write access (if using ASP.NET 2.0) or that the *ASP.NET* machine account has read and write access (if using ASP.NET 1.1). Once this is complete, we must now tell Izenda Reports which folder to use by setting the "ReportsPath" property as shown in the example.
44 44
... ...
@@ -79,7 +79,7 @@ Public Class CustomAdHocConfig Inherits Izenda.AdHoc.DatabaseAdHocConfig
79 79
80 80
###Setting the Saved Reports Table
81 81
82
-This is the most essential setting to specify when using Database Mode. However, it is not required. If it is not specified, Izenda will create and use a table called "[[IzendaAdHocReports|/FAQ/databaseadhocconfig-table-structure]]".
82
+This is the most essential setting to specify when using Database Mode. However, it is not required. If it is not specified, Izenda will create and use a table called "[[IzendaAdHocReports|http://wiki.izenda.us/FAQ/IzendaAdHocReports-table]]".
83 83
```csharp
84 84
//C#
85 85
public static void InitializeReporting()