FP2000: Enabling Database Features Without the Server Extensions
ID: Q233018
|
The information in this article applies to:
SUMMARY
The FrontPage Save to Database feature and pages generated by the Database Results Wizard can run on any server that supports Active Server Pages (ASP) and has sufficient database support for the database system you are using. Installation of Microsoft Data Access Components (MDAC) 2.1 is recommended for full support on all Windows or Windows NT-based Web servers.
Although FrontPage 2000 Server Extensions are required to create pages using these features, FrontPage Server Extensions are not required to run the pages generated by these features.
This article describes how to enable these features on Web servers that are not running the FrontPage 2000 Server Extensions.
MORE INFORMATION- If you are using a network-based data connection (to an SQL or ORACLE server) you must confirm that the network location is accessible from the destination Web. If you are using a System DSN, you must confirm that that system DSN is valid on the system running the destination Web server.
- Create your database Web. If you are using a disk-based Web, you won't be able to confirm that the pages work prior to publishing. If you are using a Web server, it must be an Internet Information Server (IIS), NT Peer Web Server (NTPWS), or Microsoft Personal Web Server (MSPWS) that
- supports Active Server Pages.
- has Microsoft Data Access Components (MDAC) 2.1 or later installed.
- has the FrontPage 2000 Server Extensions installed.
- If you are using a disk-based Web, skip to step 4. If you are using a Web server to author the pages, confirm that the pages work prior to publishing them to the unextended server.
- When the Web is complete, you can publish it using FTP or copy it using Windows Explorer or the command prompt. If publishing through FTP, enter the FTP URL for the destination in the Publish Web command by clicking Publish Web on the File menu in FrontPage 2000. If copying through Windows Explorer or the command prompt, be certain you have copied all the files from your local copy of the Web to the destination.
- On the destination server, find the entry in the Web server's configuration file(s) and make sure that the URL for the folder that you just copied or FTP published is configured as an application root. Consult your Web server or ASP provider documentation for details on this process. You must be certain that this setting is created on the HTTP URL for the published files.
REFERENCES
For additional information about when the Database menu item is disabled in FrontPage 2000, please see the following article in the Microsoft Knowledge Base:
Q232532: Database Menu Item on Insert Menu Disabled
If the published Web meets all other requirements described above, but is not an application root, you will see an error like the following when you browse to a page that uses a database connection named 'Default':
The database connection named 'Default' is undefined.
This problem can occur if:
* the connection has been removed from the web
* the file 'global.asa' is missing or contains errors
* the root folder does not have Scripting permissions enabled
* the web is not marked as an Application Root
If the published Web meets all other requirements described above, but is not an application root, you may see no error at all when submitting a database form, but no data will be added to the database on the Web server.
Additional query words:
fpodbc fpfaq front page
Keywords : kbdta
Version : WINDOWS:
Platform : WINDOWS
Issue type : kbinfo
|