-
It's still an early app, in it's 2nd to 3rd incarnation (if you count v1 SP1 as a full incarnation). Since InfoPath is on the same timeline as Office for development, features often get cut in order to meet the deadlines. That's the way with software development.
Again, it has been requested that they make every item that has text ...
-
I'm not sure what this other code is you refer to. As I understand it, when you "create" a custom toolbar button, you process it as we describe. That's it. Nothing else runs. Now I don't know everything about custom toolbars, so maybe there's some process of running some other code. In that case, here's my suggestion. ...
-
Field in the header/footer is a new feature to InfoPath 2007 and will not work in InfoPath 2003.
-
Your only other option is to create a custom XSL that will generate a WordML file... but again, this is complicated and with it's own challenges. However, since the end result is a Word document, it will have all the printing features offered by that application. I would hold this, however, as an ace up my sleeve if negotiations with the ...
-
Not currently. Tooltips are design time. We have already made that request to Microsoft for a future release, but have no control over the process of what features will make it into future releases. Just know that they are aware of that request.
-
I can't say whether it is possible (perhaps someone else would like to chime in here), but I do know that ActiveX controls have limited interfacing between InfoPath and themselves. However, for something like this, it may not be any big deal because you just looking to have the value stored away in a DOM node. My guess is that it can be done, ...
-
I don't believe that header/footer allows for tables.
-
InfoPath is sandboxed and does not allow for this. You are probably stuck using the builtin tooltip functionality.
-
Can you please provide more information, I don't follow what exactly you are trying to do.
-
It doesn't matter so much about the production environment setup. This is just for starting a new InfoPath form right? InfoPath will make a copy of all those schemas internal to the form template anyway. So just copy all the schemas into a single folder, fix them up to not have any "out of folder" references, then you should be able ...