Tutorial - Compatibility Properties - Integrating with existing ASPMaker project

Note Before reading this tutorial, please read Compatibility Properties Setup first.

In this tutorial we will show you how to put scripts generated by ASP Report Maker together with scripts generated by ASPMaker. We'll use security in both projects and demonstrate how you can make them compatible with each other.

To make ASPMaker and ASP Report Maker projects work together, there are 3 requirements:

  1. The projects share the same web folder. In general, the projects share the same application root and destination folder.
  2. The projects share the same project name.
  3. If Advanced Security is used, they shares the same Advanced Security settings, including the User ID field, Parent User ID field, User Level field and User Levels.

Project name in ASP Report Maker or ASPMaker is used in session variable to distinguish projects. For example, if the project name of your ASPMaker project is named as "project1", the session variable of the logged in status is Session variable "project1_status". If your project name of your ASP Report Maker project is named as "project2", when users browse from ASPMaker generated pages to ASP Report Maker generated pages, you will be considered as not logged in and be redirected to the login page. Therefore, to make ASP Report Maker project compatible with ASPMaker project, we need to use the same project name for both projects.

Select one of your ASPMaker projects that uses security, check the project name (see Project File) by clicking [Tools] -> [Advanced Settings].

In this example, the project name of the ASPMaker project is "demo", we'll use the same project name in ASP Report Maker.

On the other hand, ASP application generated by ASP Report Maker is self-contained, it has its own header, footer, login, logout and default page. However, if you have an existing ASP application generated by ASPMaker, you may already have those pages already. Since those pages typically have the same name like "header.asp", "footer.asp", "login.asp", "logout.asp" and "default.asp", generating your ASP Report Maker project to the same folder may create several problems:

  1. The header, footer, login, logout and default page of the existing application may be overwritten.
  2. Even if they are different (so they will not be overwritten), you'll need to maintain 2 sets of header and footer. To make the look and feel of your site consistent, you'll need to make the 2 sets of header and footer look the same too.
  3. If both projects uses security, each project has its own login and logout page, users will need to login or logout twice.

To solve these problem, ASP Report Maker allows you to enable Compatibility Properties. When enabled, ASP Report Maker will behaves a little differently during generation. If existing paths are specified, the header, footer, login, logout and default pages will not be generated so they won't overwrite existing files. Instead, the generated scripts will use the paths of header, footer, login, logout and default pages specified by the Compatibility Properties so both ASP application shares the common files. Therefore, once you have customized the header and footer for use with both ASP applications, they will not be overwritten when you re-generate scripts using ASP Report Maker.

Note If you enable Compatibility Properties but not specify the paths of header, footer, login, logout and default pages, the pages will still be generated if necessary. For example, if your ASPMaker project does not use security but your ASP Report Maker project does, you have no paths for the login page and logout page to specify, you leave them empty in the Compatibility Properties form and ASP Report Maker will generate the login and logout pages for the reports.

 

Steps to Setup Compatibility Properties

1. Make Sure the Advanced Security Settings in Both Projects Are the Same

The Advanced Security settings in both projects must be the same. Open the ASP Report Maker project you previously used in the Advanced Security tutorials (Tutorial - User ID Security or Tutorial - User Level Security). Compare the Advanced Security settings with that in your ASPMaker project. Check the User ID field, Parent User ID field, User Level field and User Levels.

Close the project. (In next step, ASPMaker may need to change your project settings, so you should not open the project in ASP Report Maker.)

2. Setting up Compatibility Properties

Compatibiltiy can be set up easily in the ASPMaker project. ASPMaker can load the ASP Report Maker project, set up above properties automatically and load the menu items from the ASP Report Maker project to the ASPMaker project. Since ASPMaker will update your ASP Report Maker project, to avoid overwriting each other, you should save your ASP Report Maker project and close ASP Report Maker first. Then in ASPMaker, open the Menu Editor, click the [Import] button in the toolbar, select your ASP Report Maker project (10.0 or later), then click [OK]. The imported menu items will be represented by orange icons, you can then re-arrange the display order of the menu items if necessary.

Note If you change User Level settings in your ASP Report Maker project later, the imported menu items in the ASPMaker project will NOT be updated automatically, you'll need to repeat above again.

If you open your report project again in ASP Report Maker and click [Tools] -> [Compatibility Properties], you should see that ASPMaker has changed some settings for compatibility:

  1. The project name has been set as the same as that of ASPMaker project,
  2. [Enable compatibility properties] is enabled,
  3. The file names of the shared files has been setup. If they are not correct, enter the file name of the header, footer, login, logout and default pages in your ASPMaker project.

 

Click [OK] to save.

3. ASP Script Generation

Go to the [Generate] tab, select the same [Application root folder] and [Destination folder] as in your ASPMaker project. Click the [Generate] button and ASP Report Maker will generate the required ASP scripts automatically.

4. Running the ASP Application

Run your existing ASP application with your browser. If use security and you have not logged in, you'll be redirected to the login page, If your ASPMaker project uses security, you should find yourself been redirected to the login page from the ASPMaker project.

Login so you can browse the existing ASPMaker pages.

Now click the new links in the menu to view the reports. You'll be redirected to the default report you specified in your ASP Report Maker project without the need to login again.

Check the User ID security or User Level security by browsing the reports and you'll find that it works as expected.

 

 

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