Custom confirmation page problem

I have developed a form in Frontpage 2000 (however my pc
is Windows XP and most of my Office applications are XP)
which are on a web server which has Windows 2000 (SP4)
installed on it.
I have created a custom confirmation page using insert
confirmation field which looks OK. However, when I try it
on the web I am encountering the same problem described
here:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;261971
ie the name of the form field to confirm is displayed in
the web browser instead of the field value.

As the resolution includes updates that are now out of
date I just wondered if the problem is associated with
something else. Please could you let me know if there is
anything else I should consider to resolve the problem.

If the web server is running the FP2000 extensions, has all of the update for the FP2000 extensions
been applied?

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
http://www.ycoln-resources.com
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp

"Jo" <anonymous@discussions.microsoft.com> wrote in message
news:9d3201c43440$12fba710$a601280a@phx.gbl...
> I have developed a form in Frontpage 2000 (however my pc
> is Windows XP and most of my Office applications are XP)
> which are on a web server which has Windows 2000 (SP4)
> installed on it.
> I have created a custom confirmation page using insert
> confirmation field which looks OK. However, when I try it
> on the web I am encountering the same problem described
> here:
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;261971
> ie the name of the form field to confirm is displayed in
> the web browser instead of the field value.
>
> As the resolution includes updates that are now out of
> date I just wondered if the problem is associated with
> something else. Please could you let me know if there is
> anything else I should consider to resolve the problem.
>
>