frontpage 2003 ASP pages display as code? Help?

[IanM]

When I use the Database wizard it creates a string of various files. When I
browse the site it has created, the HTM files all display properly. However
those with an ASP extension just display the raw ASP code. I am new to FP so
handheld direction to resolve would be much appreciated.

 

[Thomas A. Rowe]

You must view the site/page from a Windows IIS Web Server via http in order for the ASP code to be
process since it is a server-side scripting language.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
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.
==============================================

 

[Andrew Murray]

You need to view asp pages on a web server. Hence the name: Active SERVER
Pages.

If you have XP Pro and you have the IIS set up, then publish the site to
http://localhost to test it on your local machine.

 

[IanM]

Thomas/Andrew, thanks for the response. So given I have XP home edition, I
assume from your answers that there is no way to test my site until i have it
hosted by some 3rd party? If that is the case, can I use other features of
FP2003 to display/update a database just using non ASP features?
Cheers

 

[Andrew Murray]

What "other features to display/update a database just using non ASP
features" are you talking about?

All the database components to display/update/create/edit database content
in a FP web require the server extensions & ASP on a web server.

 

[Ronx]

No
Updating a database from a web page requires a web server.

You could use Apache on WinXP home, and you may be able to configure
Apache to run ASP pages and the Access database (do not ask me how!),
but it will not work with FrontPage.

Your best options are
1) Upgrade to WinXP Pro
2) Publish to a subweb on a windows server for testing, then publish
to the root web when the application is running. If there are no
links to the subweb (and you give it an obscure name), the general
public and search engines will not find the test web.