InfoPath Dev

I am migrating InfoPath 2007 form to 2010 to 2013. The form is developed in InfoPath 2007 and has code behind. I opened the form using InfoPath Designer 2013,updated data connections. When I clicked on Code Editor, code did not open, so I removed the code and hit Code Editor. It created a new Project and I added References, Web References and code and built it. Form works fine..But If I close the InfoPath designer and reopen the form again using designer, when i clicked on Code Editor it says "system cannot find the file specified". I am giving the right location, but it still says this.

I've seen this before - a client of the company I work with has a form like this, where we have to recreate the project Every. Single. Time. So annoying. If I recall correctly, it is the web references. For one of their form, I set up data connections in the form instead, and then used those in the code instead of having web service refs in the form and it started behaving correctly... You might try that. Although for their other forms, they just recreate the project each time - personally, that would drive me nuts.

Thanks for your quick response. I have data connections setup in the form and i will check if i can get rid of them in the code. I have another question here, could you please let me know if working with 2007 form in 2010/2013 would cause any issues in future. Would you suggest upgrading the form to 2010/2013. when I try to update the compatability to Web Browser 2010, it says Contact Selector control must be replaced with People Picker, but there is code related to this Contact Selector so did want to change it.

I don't recall the differences between the contact selector and the people picker. You could always try with a copy of the form and see how bad the diffs are - you may only have minimal code revisions. Is this a browser form or a filler form? If it is filler, I probably wouldn't bother to upgrade it. If it is browser, depending on the effort involved, I might - but that's because I've generally found browser forms to be a bit more troublesome (SharePoint updates occasionally causing unexpected issues, etc).

My form is browser enabled form not filler form. For now, by leaving the form as-is in 2007 and migrating it to 2010 worked fine except for loosing connection with code as discussed. But was just worried about the future issues. Thank you for your time and valuable suggestion, i will look into it.