https://www.infopathdev.com:443/forums/131.aspxqRules adds support to your InfoPath forms. With qRules, you can add features to your form that require code, but without having to write it. enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/79716.aspxThu, 21 Jun 2012 04:31:52 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:79716Jimmy0https://www.infopathdev.com:443/forums/thread/79716.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=131&PostID=79716<p>The temporary certificates that InfoPath lets you make aren&#39;t really meant to be used in production.&nbsp; The ideal approach would be to get a certificate from a certificate authority, but I realize that can be a tricky proposition for some organizations.</p><p>In lieu of that, the Digital Certificate for VBA Projects utility&nbsp;that comes with Office (it should be in your Start menu) seems to create certificates with longer expiration times.&nbsp; I just tried creating one and it had an expiration date of 1/1/2018.&nbsp; You just create the certificate, and then select it in InfoPath.</p><p>How about giving that a try?</p>https://www.infopathdev.com:443/forums/thread/79710.aspxWed, 20 Jun 2012 23:14:49 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:79710camens0https://www.infopathdev.com:443/forums/thread/79710.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=131&PostID=79710I really like the &#39;Print&#39; command in Qdabra, but am having problems with the security. When I set the form to Full Trust I have to create a certificate. These certificates expire in a couple of weeks which then creates problems for my users when they try to open it after expiration. It has gotten worse because once a certificate has expired, the form cannot be opened. I edit the form and create a new certificate, but Infopath opens the old one before updating, so I end up being locked out of the form completely. My only solution has been to stop using Print. Any other ideas?