Forms not working. Starting to hate FrontPage

[Guest]

This was posted on the FrontPage Extensions discussion but this seems a more
active site so, I'm reposting here.

I have a database results form where I filter criteria - it is working.
None of my other forms will work. I get a FrontPage error. Webmaster: See
the server's application event log. Nothing is listed for FrontPage in the
log. The pages my forms are in are named with .htm extensions. I have
carefully followed every step of tutorials and set the propper permissions
and properties. The machine I am
working on is also the server - I publish to localhost. I am at a loss as to
how to get these forms working. Everything is done with wizards so, how can
it be going wrong? Is publishing to the localhost the problem? Is there
something I need to know about configuring the server? I have reinstalled
FrontPage server extensions and created several sites to test forms. Any
suggestions? Thanks.

 

[Guest]

Is it a Windows Server?

Also, for database pages, the filename extension needs to be .asp or .aspx,
depending on whether you chose ASP or ASP.NET when you created the page.

Jim Buyens
Microsoft MVP
http://www.interlacken.com
Author of:
*-----------------------------­-----------------------
|\----------------------------­-----------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||----------------------------­-----------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/----------------------------­-----------------------
*-----------------------------­-----------------------

 

[Thomas A. Rowe]

1. The server must be Windows IIS, and you must be allowed to run ASP.
2. The forms must all have the extension of .asp

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

 

[Guest]

It is a Windows IIS server (v1.5 I believe).

Sorry I wasn't very clear. All my database forms are working - results,
editor, submission. It is any other type of form that does not work such as
a file upload form or forms where I gather info from text boxes and send it
to a formatted text file. Those two forms I inserted into .htm pages. Also,
discussion pages or guest book pages will not work and some of those do have
..asp extensions. Thanks for answering.

 

[Guest]

The server is a Windows IIS.

Sorry, I wasn't clear about the forms. All the database forms are working.
It is discussion pages or guest book pages that won't work. I create these
with the wizards and they do indead have .asp extensions. Also, forms I
insert into .htm pages won't work such as a file upload form. I try saving
these pages as .asp and they still don't work. One of the trouble shooting
tips I ran across said that I should not save the pages with inserted forms -
such as a file upload form - with extensions the same as a scripting language
that is used with the form handler - asp was on the list. I tried both
extensions, .htm and .asp, and neither worked.
Any more suggestions? Thanks.

 

[Thomas A. Rowe]

See my reply to your other post.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================