https://www.infopathdev.com:443/forums/41.aspxIf you're not sure where to ask your question, ask it here. If necessary, our moderators will make sure it gets classified in the correct board.enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/95152.aspxFri, 10 Jan 2014 19:57:10 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:95152smonczka0https://www.infopathdev.com:443/forums/thread/95152.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=95152<p>Our office has&nbsp;just migrated over to Office 365&nbsp;E3 and the Office 2013 Pro version that comes with it.&nbsp;As part of the Office Pro install&nbsp;you get InfoPath.&nbsp; It is installed automatically and there is no way NOT to include it for the user.&nbsp;&nbsp;</p><p>The issue comes up when a user gets an email as part of a workflow with a link to a form in it.&nbsp; For example a form is filled out by a sales person.&nbsp;When the form is submitted an email goes to finance notifying them.&nbsp; In the email&nbsp;is a&nbsp;link to the forml.&nbsp; The finance user clicks on the link to open the form.&nbsp;&nbsp;Instead of the form opening up&nbsp;in IE the InfoPath client pops up. This causes major confusion for the user as they have never seen and really don&#39;t want to see InfoPath. They are used to using the browser.&nbsp; This also causes other issues as forms in the client&nbsp;react differently,&nbsp;some of the functionality is slightly different.&nbsp; </p><p>Has anyone&nbsp;else run across this same problem and how did you resolve it? &nbsp;</p><p>&nbsp; </p>