SSW Access Reporter allows you to publish your important MS access reports in a variety of
popular formats, including Adobe PDF, Excel, Rich Text Format and as
HTML web pages. You can easily deliver these reports over your intranet
or public website, even if you have your database server on a different
computer to your web server.
SSW Access Reporter User Guide
1. Prerequisites
2. Running SSW Access Reporter
3. Add New Database
4. Setting up the service account
5. Using the SSW Access Reporter Client - Sample ASPX
6. Viewing report on the Web
7. Viewing report in Windows Forms
8. Running Performance Test
9. Email Notification
10. Database requirement
11. Installation Guide
|
-
Prerequisites
-
Running SSW Access Reporter

Figure: Click Access Reporter Manager taskbar icon to run Report Manager

Figure: Click Configure to change the settings
The Summary tab allows you to configure needed settings.

Figure: Check you have all green ticks
Figure: Check your PDF Settings are OK
After the PDF settings have been configured, you will need to configure
a database for access
reporter to generate reports from.
Figure: Check Database(s) are OK
-
Add new Database
On the Options form click on the "Databases" tab. Here you can add Databases. These
Databases are the
MDB's or the ADP's that contains the reports that can be generated. To configure a new Database, click on
the "Add" button, you will be required for the Database Name.
Figure: Add New Database to publish report
Figure: Set password for Database
Figure: To test the performace of publishling report, click "Performance Test" button
Figure: Input parameters to test
Figure: Result of test
-
Setting up the service account
-
In Options form, go to Service Logon tab.

Figure: The Service Logon tab to setup service account to run Access Reporter Service
-
If the account user belongs to particular domain, then the user can click the select button and select
appropriate user name from popup window.

Figure: The Select User Window for service account
-
After selecting user name, enter valid password in the Password box.
-
If the user belongs to a work group, the user can input his machine name and
username directly in the username textbox with a valid password.

Figure: The Service Logon tab with Machine name \ Domain name Example
Secondly, through the Microsoft windows Service Manager you can also modify
the user logon information:
-
From Start menu, go to Control Panel.
-
In Control Panel go to Administrative tools.
-
In Administrative Tools select Services.
-
In Services, go to the SSW Access Reporter Service.

Figure: Double Click the Access Reporter Service in the Services Window to open properties window
-
Double click on the Access Reporter Service to open the Properties window.
-
In Properties Window go to the Logon tab.

Figure: Select the Logon Tab in the Service Properties Window to change the service account
-
In the Logon tab enter the correct User name and password.
-
Click OK to complete the configuration.
If you are still getting the error message box, you need to give your
username log on as a service rights. Please follow the steps below:
-
From start menu, go to control panel.
-
In control panel go to Administrative Tools.
-
In Administrative Tools go to Local Security Policy
-
In Local Security Policy, click on Local Policies and then on User Rights Assignments.
-
Once you are into User Rights Assignments, find the 'Log On as a
Service' entry.

Figure: The Logon Service Window
-
Right click on 'Log On as a Service' and open the Properties window.

Figure: Add User or Group to use for the Access Reporter service
-
In the Properties window click on Add User or Group and then add the
user account you wish to use for the Access Reporter service.
-
Click ok to complete the configuration.
Using the SSW Access Reporter Client - Sample ASPX
In order to configure the SSW Access Report Server, we have to check a couple of things to make sure they work
and are installed correctly.
- Navigate to the directory "C:\Program Files\SSW Access Reporter\Sample". Once there try
to open ReporterSample2000.mdb Make sure that Microsoft Access opens the file and that the two reports
open and display data.
Figure: The two sample reports in Microsoft Access
- Then try the same test with the file "SSWReporter2000.adp". This file reads from a SQL database. By
default it will attempt to connect to a Local version of SQL but you can change the connection string by
going to "File" then "Connection" in Access. You will probably need to use a username and password rather
than Windows authentication.
- Open up the Report Manager and click on the "Show
Databases" button. Make sure that you have 2 jobs there, "Northwind (MDB)", and "Northwind
(ADP/SQL)". "Edit" both these jobs and
make sure that it is opening up the correct database and the report output directory is correct.
- After closing the Database Jobs page the Report Manager page pops up. Start the Report Manager by clicking on the Start button.
Figure: Click on start button to start the Report Manager
-
Viewing report on the Web
- Open your web browser and go to http://localhost/SSWAccessReporterSample1.1/ or http://localhost/SSWAccessReporterSample2.0/
- Select a Database Name, Report Name, and Report Type and click the "Submit" button.
Figure: The report page in the browser
- Hey presto, Instant report.
Figure: The sample report output in the browser
Viewing report in Windows Forms
- click on Samples on Main Form

Figure:Click on Samples button to open Winform Samples
- Choose Windows Forms 1.1 or Windows Forms 2.0 tab to run the Sample

Figure:Select Sample to view
- Click on "Create" button to create the sample

Figure:Click on create to create Sample
- Hey presto, Instant report.
Figure: The Windows forms Sample report
Running the performance test
Microsoft Access has a bug. Some complicated reports (usually ones with subforms) cause memory leaks.
If you are experiencing memory leaks, you can use the performance test which runs a suspect report many times, monitoring the memory being used.
Start the performance test by choosing a database in the Database Jobs page and click "Edit Database" to open the Database Settings page.

Figure: The Performance tab to check any memory leaks
In the tab "Memory" in this page you can enter a maximum memory limit. The SSW Access Reporter will gracefully release and recover after the report has leaked an
amount of memory greater than the value you entered here.
To run the performance test, just click the button "Performance Test" to open the Performance Test page.

Figure: Test the memory leak
Enter the database you want to use, the name of the report and a query string, for example "OrderID=1234". At last you can enter the number of reports you want to create. The default number for this value is 50.
Start the performance test by clicking the "Start" button.
Email notification
You can set up an Email Notification that sends you an Email when an error occurs.
Activate the Email Notification by choosing a database in the Database Jobs page
and click "Edit Database" to open the Database Settings page. In the tab "Performance" check the "
Email me when an error occurs with this database" check box and enter the IP address of your SMTP server, the receivers and the senders
address. To test your settings click the button "Test".
If you enable the Email Notification, an Email will be sent to you each time an error occurs when a report is created. You can also be notified when the access instance gets to the maximum memory limit. Enable this feature by checking the check box in the tab "Memory".

Figure: Setup email for any error notification
Database requirement
SSW Access Reporter works on Microsoft Access 97, 2000, 2002, 2003, but it doesn't support Query String Argument on Microsoft Access 97.
Installation Guide
To install the SSW Access Reporter, download and run the installation package from
the SSW Access Reporter Home Page
The package will install into the "Program Files" directory on your default drive. If your windows
installation is on the C: Drive, you should have minimal configuration to do, if not you will need to read
the following sections regarding how to configure the server and client.
The installation will create a program group called "SSW Access Reporter" containing a link to
the server component manager. Of the files installed during the full installation, these are of note:
- C:\Program Files\SSW Access Reporter\ReadMe.htm.
- C:\Program Files\SSW Access Reporter\SSW.AccessReporter.ReportManager.exe - the server management
component. Details
- C:\Program Files\SSW Access Reporter\Samples\SSWAccessReporterSample1.1\Default.aspx - a sample .NET 1.1 ASPX project that
uses the report server. Details
- C:\Program Files\SSW Access Reporter\Samples\SSWAccessReporterSample2.0\Default.aspx - a sample .NET 2.0 ASPX project that
uses the report server. Details
- C:\Program Files\SSW Access Reporter\Samples\WinformSamples1.1\ -
contains a sample .NET 1.1 Win Form project that
uses the report server. Details
- C:\Program Files\SSW Access Reporter\Samples\WinformSamples2.0\ -
contains a sample .NET 2.0 Win Form project that
uses the report server. Details
- C:\Program Files\SSW Access Reporter\Sample\SSWReporter2000.mdb - a sample
report database.
- C:\Program Files\SSW Access Reporter\Sample\SSWReporter2000.adp - a sample
report database that connects SQL. Details
- C:\Program Files\SSW Access Reporter\Sample\bin\ReportClient.dll - a .NET dll
that is the client component.
- http://localhost/SSWAccessReporterSample1.1 - this virtual directory is created
automatically as part of the sample installation. It points to the
ASP.NET 1.1 Sample directory.
- http://localhost/SSWAccessReporterSample1.1/reports - this virtual directory is created
automatically as part of the sample installation. It points to the
ASP.NET Sample Reports directory.
- http://localhost/SSWAccessReporterSample2.0 - this virtual directory is created
automatically as part of the sample installation. It points to the
ASP.NET 2.0 Sample directory.
- http://localhost/SSWAccessReporterSample2.0/report - this virtual directory is created
automatically as part of the sample installation. It points to the
ASP.NET Sample Reports directory.