Data Source Settings

If you are not at the [Database] tab yet, clicking the - icon in the toolbar to go to [Database] tab. ASP.NET Report Maker can connect to Microsoft Access, Microsoft SQL Server, MySQL, PostgreSQL, Oracle and other databases that supports ODBC or ADO Connection String.

1. Microsoft Access Setup

  • Select Microsoft Access as database type,
  • Select the Microsoft Access database file by clicking the - button,
  • Specify the database path where the database file will reside under the root of your ASP.NET Web application,
  • Click the - Connect button to load the database information.
Note Database path is relative to wwwroot. Use slashes "/" as path delimiter, no leading slash. e.g. If the wwwroot of your website is C:\MyProjectFolder\wwwroot and you enter "data/" in this textbox, the folder for the database will be C:\MyProjectFolder\wwwroot\data. If not specified, the default is the wwwroot folder. It is OK to put the database in the wwwroot as .mdb files are not served by the application by default. If you are not sure which folder is wwwroot, please read Generate Settings.

-

2. Microsoft SQL Server Setup

Note

  1. If you have installed SQL Server 2012 Native Client (x86) on your computer, then Microsoft SQL Server database type will be available for selection. You can use this database type for connection to SQL Server 2005 or newer. You can download SQL Server 2012 Native Client from the Microsoft website. See System Requirements. The native client must also be installed on the web server. (ODBC or the old OLE DB provider for SQL Server are NOT supported.)
  2. ASP.NET Report Maker connects to the SQL Server by TCP/IP (NOT Windows authentication), make sure TCP/IP protocols is enabled for your SQL server, you can use SQL Server Configuration Manager to check and configure.
  3. If the SQL Server is a remote server (not on the same machine as ASP.NET Report Maker), make sure your SQL Server allows remote connection, you can use SQL Server Management Studio to check and configure.
  4. If you have firewall enabled on the server, make sure it allows inbound traffic on port 1433 for TCP/IP. If the SQL Server uses another port number, make sure you have set up the firewall rules accordingly. 
  • Select Microsoft SQL Server as database type,
  • Enter the name or IP of the SQL server,
  • Enter the User ID and Password,
  • Select the database you want or just enter the name of your database,
  • Click the - Connect button to load the database information.

Note

  1. If Microsoft SQL Server 2005 or newer, make sure the server name includes the instance name, e.g. localhost\SQLEXPRESS.
  2. The server name or IP should be valid on your production Web server also. Otherwise you'll need to modify the generated connection string in ewrcfg*.cs before you upload it to your production server. For example, if you have a testing SQL Server installed on the same computer, you can use "(local)" as server name when you connect to it with ASP.NET Report Maker. The generated scripts will then try to connect to a SQL Server on the same computer as the production Web server, if this is not the case on the server, the connection will fail. It is common that SQL Server is installed on a different server in production environment.
  3. If you want to use trusted connection with integrated authentication, you can connect using Connection String (see section below). However, note that in this case you'll need to make sure the Web sever user has appropriate access to the database. Otherwise, you will most likely see an error message such as "Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.", when you try to launch your ASP.NET application.

-

3. MySQL

  • Select MySQL as database type,
  • Enter the name or IP of the database server,
  • Enter the User ID and Password,
  • Select the database you want or just enter the name of your database,
  • Click the - Connect button to load the database information.
Note The server name or IP should be valid on your production Web server also. Otherwise you'll need to modify the generated connection string in ewrcfg*.cs before you upload it to your production server. For example, if you have a testing MySQL Server installed on the same computer, you can use "localhost" as server name when you connect to it with ASP.NET Report Maker. The generated scripts will then try to connect to a MySQL Server on the same computer as the production Web server, if this is not the case on the server, the connection will fail.

-

 

4. PostgreSQL

  • Select PostgreSQL as database type,
  • Enter the name or IP of the database server,
  • Enter the User ID and Password,
  • Select the database you want or just enter the name of your database,
  • Click the - Connect button to load the database information.
Note The server name or IP should be valid on your production Web server also. Otherwise you'll need to modify the generated connection string in ewrcfg*.cs before you upload it to your production server. For example, if you have a testing PostgreSQL Server installed on the same computer, you can use "localhost" as server name when you connect to it with ASP.NET Report Maker. The generated scripts will then try to connect to a PostgreSQL Server on the same computer as the production Web server, if this is not the case on the server, the connection will fail.

-

 

5. Oracle

NoteIf you have installed Oracle client on your computer, this database type will be available for selection. You can download Oracle client from the Oracle website. Make sure the path of your Oracle client (e.g. oci.dll) is among the Path variable under Windows Environment Variables -> System variable.
  • Select Oracle as database type,
  • Enter the Oracle Service name,
  • Enter the User ID and Password,
  • Select the Schema you want or just enter the Schema name,
  • Click the - Connect button to load the database information.
Note The service name should be valid on your production Web server also. Otherwise you'll need to modify the generated connection string in ewrcfg*.cs before you upload it to your production server. The service name must be set to the appropriate Net8 name which is known to the naming method in use. For example, for Local Naming, it is the alias in the tnsnames.ora file; for Oracle Names, it is the Net8 Service Name.

-

 

6. ODBC

  • Select ODBC as database type,
  • Select a System DSN from the dropdown list. You can create or modify a System DSN by clicking the [...] button,
  • Enter the User ID and Password,
  • Click the - Connect button to load the database information.
Note You should create a DSN with the same name, user ID and password as that on the production Web server. Otherwise you'll need to modify the generated connection string in ewrcfg*.cs before you upload it to your production server.

-

 

On completion, the tables and fields information will be loaded and displayed on the left hand side.

The database pane is dockable. If you prefer to display the database pane on the right hand side, simply drag it to the right side.

-

 

Dynamic Table Loading

By default all tables are loaded upon first connection. It is convenient but loading and synchronization could be slow if your database contains a large number of tables or fields. In such cases you can choose to load the tables dynamically, a table will only be loaded when you select it in the database pane. If you just use a few tables out of a large database, this feature enables you to work much faster. To enable this feature, simply check [Load tables dynamically] before pressing the [Connect] button.

 

 

 ©2007-2017 e.World Technology Ltd. All rights reserved.