Ok, I stand corrected regarding the fact that you can at least create a form in Publisher 2002 and
2003 and then uploaded via Web Folder (http) to a remote server that has the FP extensions and the
form will work as long as the web host has configured the extensions to process email. As far as the
default confirmation page, users do not have any control over it, whether using FP or not.
However, using Publisher 2002 or 2003 there are other issues... mainly because Publisher is a
desktop publishing application, not a web development application, it just has the ability to save
it documents in HTML, just like Word and PowerPoint, etc.
1. you do not have the ability to deal with any of the FP extensions features available via FP from
within Publisher, you can't even see what version of the FP extensions are installed on the server.
2. you can not edit individual pages and then just upload those individual changes pages, instead
you have to upload the entire site again, nor can you make any change on the live/remote server and
then import those change back into your original document.
3. you have very limited control over the form data format, other then to select what is to happen
to the form data (stored in a folder, email or processed by server-side form handler). You can not
send to both a file and email at the same time or apply any form field validation.
http://www.ecom-data.com/webpub/pubweb.htm (Publisher 2002)
(I see no way to fix the form page from within Publisher once it have been save as a web.)
http://www.ecom-data.com/webpubp1 (Publisher 2003)
I will say that MS has done a better job of having the Publisher's generated web pages, display in
different browsers better.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
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.
==============================================
David Bartosik said:
Thomas, you are incorrect. The form controls of Publisher are FrontPages. Remember that Office
always shares code objects across Suite products. While Publisher's form functionality is not as
robust as FP, it does still use, requires, the Frontpage Server Extensions. This is all built into
Publisher and invisible to the customer. The customer only has to publish via http a Publisher
form to a FPSE ready server to achieve a functional form.
This Publisher customer posted this thread at my request. As such I consider this as much a post
from me as it is the customer.
In my 5 years of being a Publisher MVP I have not once encountered this customers issue. In fact
as long as the publisher web is published in http to a FPSE ready server there is never an issue.
I hope a possible resolution of the issue can be achieved here in the public forum to serve the
customer.
David Bartosik - [MSFT MVP]
http://www.publishermvps.com
http://www.davidbartosik.com
Thomas A. Rowe said:
If you use Publisher 2003, then any thing that requires the FP extensions will not work, unless
you edit the page with FP and then publish it.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
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.
==============================================
