Our website is based on a commercially-hosted site, where the ISP runs W2K / IIS 5.0.

The webpages were originally created under FP2K; we recently purchased FP2002 and as soon as we used it to modify files all hell broke loose.

Basically, on 'File Save', things would lock up, and the only recourse was to use Task Manager to force an exit.

This appeared to leave the file in question in an anomalous state, looking as if (perhaps) it was still open, waiting to close.

At that point, any system-wide actions (Reports, Recalculate Hyperlinks ...) would fail when a reference was made to the folder containing the offending file.

It took the ISP and myself some 10 working days of uploads and downloads to clear things up; the ISP now says that they will not support the use of FP2002 until Microsoft fixes the problem.

I have not been able to find anything about this problem on the MS site -- does anyone have any information?

JimHH

quote:

---

Originally posted by JimH:
[Our website is based on a commercially-hosted site, where the ISP runs W2K / IIS 5.0.

The webpages were originally created under FP2K; we recently purchased FP2002 and as soon as we used it to modify files all hell broke loose.

---

Mmmmm.... How are the pages being edited? "LIVE" on the server or locally on a workstation and the published to the hosting server?

Rian

------------------
"Designing The Future"
SR Web Creators
http://www.srwebcreators.com

"What boots up must come down..."

"Mmmmm.... How are the pages being edited? "LIVE" on the server or locally on a workstation and the published to the hosting server?"

It's a mix of both. Two of us work with the site: we prefer to perform routine updates locally (on an NT 4.0 / IIS 4.0 server), but some changes can only be tested on site (e.g. some recent server-side and mail-handling work). It's a lot more convenient to edit on site with the latter category.

Even so (and I don't want to take the risk of re-checking this!) I am fairly sure that FP2002 changes made locally resulted in post-publication errors on site.

Thanks for the response,

JimH