c1c97b0a7425aa9badfc924b0bb45a63e702ddb0
API/AdHocContext.md
| ... | ... | @@ -13,7 +13,7 @@ The AdHocContext class is used to setup the database driver, access the report s |
| 13 | 13 | |CurrentUserName|Gets the AdHocSettings.CurrentUserName property for backwards-compatibility reasons| |
| 14 | 14 | |Driver|Gets or sets the database driver that your application will use| |
| 15 | 15 | |ProcessorLicenses|Gets the maximum number of processors your current license key can support| |
| 16 | -|ReportSetCount|Not used| |
|
| 16 | +|ReportSetCount|Not used internally| |
|
| 17 | 17 | |SchedulerExecuting|Gets a value indicating whether the Izenda Scheduler is executing scheduled reports or not| |
| 18 | 18 | |SetSchedulerExecuting|This method takes a boolean value that sets whether or not the Izenda Scheduler is executing| |
| 19 | 19 | |StoreInStaticMemory|Gets or sets whether the CurrentReportSet will be stored in static memory or not| |
| ... | ... | @@ -50,6 +50,8 @@ AdHocContext.Driver = new MSSQLDriver(); |
| 50 | 50 | |
| 51 | 51 | The default value is a new MSSQLDriver. |
| 52 | 52 | |
| 53 | +_**Note:** You should refrain from using the **.Driver** property when working with requests to the database in custom methods, such as with [[ProcessDataSet|http://wiki.izenda.us/FAQ/ProcessDataSet]]. This can interfere with how Izenda works internally and cause various portions of the application to stop functioning correctly._ |
|
| 54 | + |
|
| 53 | 55 | ##SchedulerExecuting |
| 54 | 56 | |
| 55 | 57 | Normally, this setting will be automatically updated when your rs.aspx is called with the run_scheduled_reports=1 parameter. You can also update this value yourself if you need special kinds of scheduling. This can be done in PreExecuteReportSet and PostExecuteReportSet respectively. |
| ... | ... | \ No newline at end of file |