Enable multi-language project. If enabled, a combobox will appear on the top of the generated scripts for user to select language. See Tools for selecting languages for the multi-language project.

Important Notes:

1. Multi-Language project must use utf-8 encoding. The charset of the project must be "utf-8".
2. The data in your database must be stored in unicode, otherwise your data will not be displayed properly.
3. If you have customized the template and put unicode characters in the template directly instead of using language files, enable the Advanced Setting UTF-8 output files (see Customizing Template and Tools).

Default language of the project. It must be compatible with Charset (see HTML Settings). Default is English.

There is always one default language for a project. Only the English language file (english.xml) is shipped with ASP.NET Report Maker. If your project is single language but you use another language, create a language file for your language (see Customizing Template), put it in the "languages" subfolder under the installation folder and then select your default language using this combobox.

If you enable Multi-Language, you must select one of the selected languages as the default language.

Enable server-side form validation for Extended Filter.

Note: If the available validation format in the Report Field Settings panel (see Field Setup) does not fulfil your requirements, you can use your own server-side validation code using Sever Event and Client Scripts.

Enable Client-side (JavaScript) form validation for Extended Filter.

Note: If the available validation format in the Report Field Settings panel (see Field Setup) does not fulfil your requirements, you can use your own client-side validation code using Sever Event and Client Scripts.

File folder for images, export-to-email, and email log file.

Notes:

1. If you use export-to-email or email log to text file, you must grant write permission to this folder on your server so the script can write files in this folder.
2. If you have field specific file folder, set it in the View Tag panel (see Field Setup).

Records can export to HTML, Excel, Word or Email. HTML format is used as a printer friendly version.

Notes:

1. When exporting to Email, the user can select sending the records as URL or HTML. If sending URL only, note that the recipient will need to click the URL and go to your site to view the records. The exported page is stored in the File Folder specified above. If sending HTML and the report contain charts, the chart still needs the Flash file (.swf) to chart the data, the .swf file is retrieved from your site, so the user must be online in order to view the charts.
   
   
2. If the report contain charts, the charts cannot be exported to Word and Excel, only report data can be exported.

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 your output file extension, e.g. .aspx), 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.

Export type - Determines what to export. The follows are supported:

• All Pages - Records in all pages are exported
• Current Page - All records in current page are exported

VB - VB.NET Codes will be generated
C# - C# Codes will be generated

Note: When you change the language, all the language-dependent settings in the project such as server events will become inapplicable, you'll need to convert your code in those settings also. ASP.NET Maker will NOT convert the code automatically.

Target .NET Framework version of the project, available options are 2.0, 3.5 or 4.0. ASP.NET Maker scripts require .NET Framework 2.0 only, you should only select 3.5 or 4.0if you plan to add your own code that requires 3.0, 3.5 or 4.0.

Note: The only differences in the generated scripts are the configurations in the web.config. All other generated code is the same in these versions.

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-behind file is checked, ASP.NET Maker will use this model.

Various options for setting up the web.config.

ASP.NET 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.

The host name or IP of the SMTP server.

Note: Some servers do not support "localhost" as SMTP server, in such case you need to specify a valid SMTP server in the network.

User name for SMTP server authentication. If your SMTP server does not require authentication, leave it blank.

Password for SMTP server authentication. If your SMTP server does not require authentication, leave it blank.