Using FrontPage with ASP

Follow this FrontPage tutorial to find out how FrontPage offers several features that make it simple to add interactive database connectivity to your Website. You can:

  • Easily incorporate database queries into your site.
  • Choose from several different methods for displaying the database information.
  • Create a custom form in minutes and send results to an existing database.
From: http://www.chilisoft.com/caspdoc/.

Once a connection is made to a database, FrontPage makes it easy to display data on a Webpage with the Database Results Wizard. By displaying the contents of your ODBC database on a Webpage, users will see the most recent data each time they view and refresh a page.

Please contact Netregistry Support if you wish to utilise database features.

FrontPage Database Features

FrontPage Data Connections

FrontPage uses FrontPage Database Connections to specify the name, location, and type of database to access, along with any driver-specific information, user names, passwords, etc. You enter this information in FrontPage, and it is written to the global.asa file as a Connection String.

File/Folder Database Connections

FrontPage supports direct access to database files for file-based databases such as Access, dBase, FoxPro, Excel, Paradox, Excel, .txt, .csv, etc. FrontPage constructs a Connection String for the file and stores it in global.asa. The following example shows the ASP code written to global.asa for a dBase database:

Application("InvSampInWeb_ConnnectionString") = "DRIVER={Microsoft dBase Driver (*.dbf)}; DefaultDir=URL=invsamp/"

The "URL=" parameter signifies that the DefaultDir is a Web-relative path. Script in global.asa maps this relative path to an absolute file system path required by the driver.

Click here, if you are using Netscape, for an example of the code for an Access Database. Stop, if you are using MicroSoft IE, you will need to click here for an example of the code for an Access Database.

Click here, if you are using Netscape, for an example of the code for an Postgres Database. Stop, if you are using MicroSoft IE, you will need to click here for an example of the code for an Postgres Database.

Note: Excel file connections are not supported on UNIX or Linux. Chili!Soft ASP for UNIX/Linux can connect to an Access database, but the Access database must reside on Windows NT, please contact Netregistry Support for assistance..

Custom Connections using File DSNs

For assistance with custom connections, please contact Netregistry Support.

Users can create File DSNs that connect to ODBC data sources using the Microsoft ODBC Admin tool. Once the resulting *.dsn file is imported to the Web, FrontPage users can create a connection that points to it. Note that if you are using a file-based database such as dBase, your *.dsn file will contain a hard-coded file reference that may not work when moved to a different server.

The Connection String constructed by FrontPage would look like:

Application("Inventory_ConnectionString") = "File Name=URL=/Inventory_file_dsn.dsn"

A File DSN can be stored in protected directories available only to the Chili!Soft ASP server and the user that created it. The use of File DSNs is typically the most secure approach to providing database access on a shared Web server because the File DSN can contain the user name and password for the database, and when Chili!Soft ASP is running in Inherited User mode, it can only open the file containing the DSN if it is running as a user with permission to open the file.

Chili!Soft ASP and the FrontPage Server Extensions

Chili!Soft ASP supports FrontPage-generated ASP applications on Linux. Included in the FrontPage package are "FrontPage Server Extensions" that enable users to create Webpages for a variety of Web Servers. You may use Chili!Soft ASP and the FrontPage Server Extensions together with the same Web server. There are two points to remember, however.
 
First, when Chili!Soft ASP and the FrontPage Server Extensions are together on the same machine, you cannot create author ASP pages directly. You must first create any ASP pages generated by the Database Results Wizard on your local workstation (by using a disk-based Web, Personal Web Server, or IIS). After the pages are moved to the remote server running Chili!Soft ASP and the FrontPage Server Extensions, you can use FrontPage to alter the ASP or HTML pages directly.
 
Second, if you are using Chili!Soft ASP and the FrontPage Server Extensions together with the Apache Web server on Linux, you will need to obtain a special version of the Chili!Soft ASP module for Apache. Further details are provided in the Configuring Apache topic of the Chili!Soft ASP for Linux Installation sections. See http://www.chilisoft.com/caspdoc/

Contact Netregistry Support from more information on database connectivity, database features and connections using file DSN.

Important Facts to Remember

Remember the following when creating and deploying FrontPage ASP application Websites with Chili!Soft ASP:

  • Chili!Soft ASP for UNIX or Linux can dynamically recognize ASP applications created by FrontPage 2000 & 2003, but only if the application is not in a nested subweb. Contact Netregistry Support if you need assistance with this.
  • Access databases will run with Chili!Soft ASP on Windows NT, but they will not run on UNIX or Linux servers.
  • If you are converting Access to dBase, convert the database (using the Access Export table feature) and import the resulting folder of files to your FrontPage web. Then use the Database Results Wizard.
  • If you have moved your dBase-based Web application to UNIX, and Chili!Soft ASP can't open your database, make sure that file extension of your dBase files is all caps (i.e. *.DBF.)
  • dBase databases do not support multi-table joins on UNIX.
  • If EnableParentPaths is False in the Chili!Soft ASP registry, the CreateObject("Scripting.FileSystemObject") calls generated in global.asa by FrontPage will not work. Either change EnableParentPaths to True (the default), or change the code generated by FrontPage in the global.asa file to Server.CreateObject("Scripting.FileSystemObject").
© 1997- 2008 Netregistry Pty Ltd