-
Hi again,
If the CAs are in domains that trust one another, it should work, but if they're in separate domains, you'll have to use certificates issued by a company like Verisign (i.e. people will have to have their own).
-
Hi Beth,
Unfortunately, you have to use code to do this. Take a look at the js code in the Timesheet (Detailed) sample. It has code to calculate the totals I think (see common.js). Good luck!
-
Hi Dennis,
Sorry for the delay in responding. I actually read your post but didn't have time to respond last week and then our web server went down and we had to jump on that. Anyway, glad to see you figured it out! :)
-
If the InfoPath AppDomain control assembly does not have full trust permissions – which it will on a normal machine, InfoPath may fail to open. This may be due to a corrupted CAS. It only happen with InfoPath solutions that contain managed code. Resetting CAS settings (caspol –rs) on the machine with the problem is the easiest way to ...
-
Hi Bernie,
Are the certificates that you are using to sign the forms issued by the same Certificate Authority?
-
Doesn't the protection feature just show a dialog box when they open the form in the designer? I didn't think it prevented the user from seeing the code. Maybe I'm wrong though.
Hi Rggg and welcome,
Another way to do this is to use managed code (.NET) and obfuscate the code that you create. I heard somewhere that obfuscation was built into Visual ...
-
Hmmm. System.XML works now with InfoPath 2007. Do you have the Beta2?
-
Hi again,
Sorry for not responding sooner. I'm going to ask our DB experts to look at this thread. Lately, we have had some of the same problems, so hopefully it will be an easy resolution. More soon!
-
Hi Thierry,
*Your* French forum has some of the most active threads! I think I need to send you stock in InfoPathDev or something. :)
Not sure if this will help you, but have you tried:
if (((IXMLDOMElement)NextCase).getAttribute(''xsi:nil'') != null)
((IXMLDOMElement)NextCase).removeAttribute(''xsi:nil'');
Good luck!
-
Hi Buki,
My guess is that it's a bug in your custom import code. I'd have to look at that. Sorry for not responding sooner!