Undo automatic save on publish IF 2007

[stephenh2]

I selected to automatically save template files when publishing. I
would like to reset this feature to the default which is publish
without saving the file. How do I reset this?

 

[S.Y.M. Wong-A-Ton]

The default was never to publish without saving the file. The default is to
prompt you to save the file before publishing it instead of directly going to
the "Save As" dialog box. This is what the original dialog box says before
you check the option to "Always save the form template when publishing":

This form template must be saved before it can be published. Click OK to
save or Cancel to continue working.

So the file *must always* be saved before you can publish it, whether you
are using the default option (prompt) or not. Having said that, I agree that
there should be or have been an option somewhere to revert back to being
prompted to save the file before publishing. I could not find that option
anywhere, so I'm guessing it was not added.

 

[stephenh2]

I store current IP templates in a network share folder for my staff to
link to. With IP 2003, If I needed to update the forms, I could make
changes, save them at the published site and users would be notified
that an updated form was available when they opened the template.

Now, when I update a form and save it, it says that the network name
is unavailable. I have to save the template with a different file name
and remove the old template. I am looking for a way to maintain my
templates without having to rename them every time I open them in
design mode.

 

[S.Y.M. Wong-A-Ton]

That sounds like odd behavior. Can you please list the exact steps you take
so that I can try to reproduce it?

From your post I understand that you have old InfoPath 2003 templates and
that you're trying to open them in Infopath 2007. Correct? And when you open
them in design mode, InfoPath 2007 prompts you to save them, but shows the
message that the network name is unavailable. I'm I still warm?

 

[stephenh2]

Yes, that is correct. I created a form in Infopath 2003 in design mode
on my local PC. I then published it to a network shared folder.

I have since installed Infopath 2007. I opened the form in design mode
to make some changes. Once I click save, it get the error message:
Infopath cannot save the following form: "Form Name." The specified
network name is no longer available." It then opens up the Save As
windows showing the current location of the form in its network
folder. The default name is the same same. I hit save to overwrite the
current copy (which I coud do in Infopath 2003), but the same message
appears. If I change the file name, I can save it in the same current
network folder as the original template that I was working on.

Now, If I open a template in design mode in its network location, I
have the same problem if I want to republish it to another site. I
select publish from the file menu. It shows the message that changes
have been made and the form will be saved when the publish wizard is
completed. The wizard runs correctly and I can publish it to its new
network site, but when it tries to save it in its current network
location after the publish is completed, I get the same message.

It seems as if that the new form cannot overwrite the old form. This
behavior did not occur with Infopath 2003.

 

[S.Y.M. Wong-A-Ton]

Thank you for the additional info. I'll try to set up an environment and see
whether I can reproduce it. I'll get back to you on this.

 

[S.Y.M. Wong-A-Ton]

I had a quick look for you, but was not able to reproduce the issue. So I'm
guessing that it could have something to do with you network policy? Have you
already tried it on forms that were published elsewhere?

 

[stephenh2]

Yes, I was able to save and republish forms under infopath 2003. I
have been using infopath forms for about 9 months

 

[S.Y.M. Wong-A-Ton]

Yes, you said that before. I meant, did you try doing the same with forms
that were created with InfoPath 2003 and published elsewhere than on the
network, and try opening them with InfoPath 2007? That is, have you tested
other publish locations with the 2003/2007 combination?