ASP.NET SettingsGeneral Options

| CodePage |
Codepage to be used for your web site |
| LCID |
Locale ID to be used for your web site |
| Default Date Format |
yyyy/mm/dd, mm/dd/yyyy, dd/mm/yyyy,
yyyy-mm-dd, mm-dd-yyyy, dd-mm-yyyy,
yyyy.mm.dd, mm.dd.yyyy, dd.mm.yyyy |
| No Cache |
Whether caching is required on browser |
| Replace CR+LF by <br> |
For memo fields |
Report Page Options (Global)
The following report page options are global for all tables. If you want different settings for a particular table, you can use table-specific options available in the Table Setup page.
| Records per page |
Number of records to be displayed on the list page of all tables.
If blank or 0, default setting of 20 will be used.
Note: When the report has grouping levels, this setting refers to number of groups (specifically, number of records from the highest level group) per page. |
| Selectable page sizes |
Number of records to be selected by user. Comma separated values,
e.g. 10,20,50,ALL.
Note: "ALL" (without
quotes) is supported, other values must be integers. |
| Paging section style |
"NumericPages" or "NextPrev" |
| Paging section at top |
Show the paging section at top instead of bottom |
| Export |
Records can export to HTML, Excel, Word format.
HTML format can be used as a printer friendly version.
Known Internet Explorer issue:
For known MIME (Multipurpose Internet Mail Extensions) types such
as Microsoft Word ("application/ms-word"), the default behavior
of some older versions of Internet Explorer is to open the document
in the browser. Also, to allow user saving the file with a proper
file extension (otherwise the file extension will be .asp), ASP.NET Report Maker
uses content-disposition header to override this behavior by default.
For example:
Response.AddHeader("content-disposition","attachment; filename=fname.ext")
When
Internet Explorer receives the header, it raises a File Download
dialog box. However, if user clicks [Open], Internet Explorer
may fail to open the file. Therefore, you may want to instruct
user to save the file directly to the user's disk without opening
it in the browser. |
1.2 .NET-Specific Options

| Language |
VB - VB.NET Codes will be generated
C# - C# Codes will be generated
|
| Use code separation |
ASP.NET provides two ways that you can organize code within your pages:
code-inline - it is very useful when you want to
maintain your code and presentation logic in a single file. By default
ASP.NET Maker uses this model.
code-behind - the code for handling events is located
in a physically separate file from the page that contains server
controls and markup. If Use code separation is checked, ASP.NET
Maker will use this model. |
| Web.config |
Various options for setting up the web.config.
ASP.NET Report Maker generates a configuration file (web.config) for each project.
The web.config file contains a nested hierarchy of XML tags and subtags with
attributes that specify the configuration settings which control how ASP.NET Web
applications behave. Here you can easily specify settings to many commonly used elements such as
authentication, sessionState and trace.
For detail description
of each field please refer to the Microsoft
.NET Framework SDK.
Note: For compatibility of existing ASP.NET application generated by ASP.NET Maker, please read Compatibility Properties Setup.
|
|