Re: Infopath 2013 "save as" with code

GeneralK2 — Tue, 18 Feb 2014 15:41:53 GMT

Yes, I am too. Did you find a solution for matching the new form to its own code folder?

paolo — Fri, 14 Feb 2014 07:38:33 GMT

Anyone else having this issues? Or is it just me?

Infopath 2013 "save as" with code

paolo — Wed, 12 Feb 2014 16:57:50 GMT

Hallo,

I was recently upgraded from Infopath 2010 to Infopath 2013.

I noticed a very weird behavior, and I wonder if there is some setting hidden somewhere to change it...

On Infopath Designer 2010 if i have a form template with attached VB (or C#) code, let's say it is

called "Dog", I would have a Dog.xsn file and a folder called Dog (living in the

"Project Location for Visual Basic and C# code" as defined in the form option window)

that would contain the code part. If I did a "Save As" and saved the "Dog" form with the new name

"Cat", it would automatically create a "Cat" folder in the "Project Location for Visual Basic and C# code"

that would contain an exact copy of the Dog code, and both form templates would be properly connected

to each folder (connected here means which code is opened from the "Developer -> Code Editor"

and compiled when publishing the template).

Now on Infopath Designer 2013, this does not happen anymore. Rather, after doing a "Save As Cat"

on the "Dog" template, I have the two form templates "Dog" and "Cat" that are both connected to

the code in the "Dog" folder. I find this behavior rather unhelpful, and I would like

to go back to the old behavior I had in Infopath 2010. Any suggestions on how to achieve that?

Thanks,

Paolo Grigis

ABB Switzerland