FP web problems when moving from IIS 5 to IIS 6

[schabala]

I am assisting a user in moving their FP web from a Windows 2000
Server running IIS5 to a Windows 2003 Server running IIS6. The first
problem we encountered was the "Incomplete query clause" error message
on many of his Database Results screens. The solution posted on this
board (thanks!) with replacing "" with [] seeming to work but the user
is concerned that all the formatting with the Database Results wizard
will be lost if he has do a custom query for each Database Results
screen. Is there any way to do mass change on these Database Results
screens to change "" to [] without redoing every Database Results
screen?

Thanks for your help,
Steve Chabala

 

[Myron Johnson]

I am assisting a user in moving their FP web from a Windows 2000
Server running IIS5 to a Windows 2003 Server running IIS6. The first
problem we encountered was the "Incomplete query clause" error message
on many of his Database Results screens. The solution posted on this
board (thanks!) with replacing "" with [] seeming to work but the user
is concerned that all the formatting with the Database Results wizard
will be lost if he has do a custom query for each Database Results
screen. Is there any way to do mass change on these Database Results
screens to change "" to [] without redoing every Database Results
screen?

Thanks for your help,
Steve Chabala

Steve,
I was the one who posted about fixing DRW queries by replacing the ""
with [] in a custom query.

What I've found is that FrontPage/IIS 6.0 has problems with the
following:

1) Hypens in Query Names
2) (Maybe) Spaces in Query Names
3) Hypens in Database Field Names

You can save a LOT of grief by:

a) Removing all hypens in both Query Names and Database Field Names
b) (possibly) Removing all spaces in Query Names

I haven't gotten to the bottom of issues with FP and IIS 6.0 regarding
spaces in query names, but I do know that FP 'bots hate hypens (they
think they are "minus signs").

In general, converting to IIS 6.0 has been a real pain. I had to do a
lot of re-writing to make my totally functional (IIS 5.1) site work
with IIS 6.0. The latest problem is the .ASP page caching feature
(bug) of IIS 6.0. Eventually it becomes totally disfunctional and
starts unpredictable (and apparently unfixable, even with rebooting)
caching of .ASP pages. I had to turn .ASP caching off on my server in
order to continue working on the site. I'd make an .ASP change and it
would NEVER refresh on the site.

Myron

 

[Myron Johnson]

1) Hypens in Query Names
2) (Maybe) Spaces in Query Names
3) Hypens in Database Field Names

Whoops! Please do a Search and Replace!
Hypens = Hyphens!

Sorry,
Myron

 

[Bob]

I had to turn .ASP caching off on my server in
order to continue working on the site. I'd make an .ASP change and it
would NEVER refresh on the site.

There were similar caching problems in earlier versions of the server.
They just don't seem to have the caching-development scenario worked
out.