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/4580.aspxThu, 10 Mar 2005 21:37:07 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:4580Patrick Halstead0https://www.infopathdev.com:443/forums/thread/4580.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=4580<b>Problem</b><br />There is no intrinsic way to lock an InfoPath form to prevent someone from opening it in design mode or using a zip utility. Do you have any suggestions as to how this might be done?<br /><br /><b>Solutions</b><br />Yes, the protect option in InfoPath is a bit flimsy and doesn#%92t prevent someone from cracking the form. This leads to a host of privacy issues. <br /><br />Some random ideas:<br /> <ul><br /><li>Use online secondary data resources for sensitive data. <br />we typically do not use secondary data resources (2DS) in the solution when there are privacy concerns. </li><br /><li>If you must have offline, encrypt the data into a binary file and have your .NET assembly in InfoPath decrypt it based on a key<br />the .NET assembly is compiled so slightly harder to crack<br /> </li></ul><br /><br />Hope this helps!