C
Cathi Odtohan
We recently upgraded our WindowsNT 4.0 server with IIS 4.0 to WindowsServer
2003 with IIS 6.0.
EndUsers are using FrontPage Server 2002 to generate web pages.
One of the security features of IIS 6.0 is default disabling of Parent
Paths. Unfortunately, when FrontPage 2002 generates *.asp pages using the
Database Results Wizard, the #include statements always use relative parent
paths. Is there a way to make FrontPage2002 use absolute paths? Is this
problem resolved in FrontPage2003?
Any advice is appreciated.
Thanks!
2003 with IIS 6.0.
EndUsers are using FrontPage Server 2002 to generate web pages.
One of the security features of IIS 6.0 is default disabling of Parent
Paths. Unfortunately, when FrontPage 2002 generates *.asp pages using the
Database Results Wizard, the #include statements always use relative parent
paths. Is there a way to make FrontPage2002 use absolute paths? Is this
problem resolved in FrontPage2003?
Any advice is appreciated.
Thanks!