E.4 Important Facts to Remember

Remember the following when creating and deploying FrontPage ASP application Web sites with Chili!Soft ASP:
- When using the Database Results Wizard, create your pages locally on your workstation first (using a disk-based Web, or Personal Web Server), and then move the pages to the Chili!Soft ASP server.
- Chili!Soft ASP for UNIX Linux can dynamically recognize ASP applications created by FrontPage 2000, but only if the application is not in a nested subweb. If the application (and its associated Global.asa file) is located in a directory that is not a top-level directory of your Web's document root, then you will need to define this application using either the [applications] section of Chili!Soft ASP's casp.cnfg file, or by adding an alias to your Web server's configuration. See Chapter 5: ASP Reference for more details.
- Remember to create any System DSNs that you refer to in your FrontPage ASP application on the Chili!Soft ASP server, or use "DSN-less" connections.
- Access databases will run with Chili!Soft ASP on Windows NT, but they will not run on UNIX or Linux servers. Use dBase databases instead.
- 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 UUNIX, 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").
Copyright © 2000 Chili!Soft
|