What Microsoft InfoPath 2010 Can't Do

I feel like there are many sites/blogs/articles etc that list all the wondrous things that InfoPath can do.  They praise how user friendly it is for non-coders, how quick it is to design forms in comparison to Adobe & Visual Studio.  What none of them tell you is that if you want to design a code-less InfoPath form, you are severely restricted in many areas that you wouldn't realise, until of course you need to implement that functionality.

"Why would you need to stick to a code-less InfoPath form?" you ask?  Well, in our organisation, the reason is simple.  We plan on creating many automated forms, and we plan on pushing them out to the various departments so that they can administer small changes themselves, only asking for help when they need technical advice.

So as a coder who knows what can be achieved with a cheeky bit of C# here and there, I am going to list of issues I've found while trying to create a code-less form:

- Insert images in Headers & Footers

- Query databases dynamically

- Email the form as a proper attachment

- Drop-Down Lists: cannot display more than one field of information on each  line.

- Using InfoPath on a Tablet:  If you accidently double-tap, it zooms in, with no way to zoom out without exiting the form and re-opening it. 

-

-

-

-

-

-

-

-

-

Obviously there are a lot more issues I wish to list, but right now I have a few things to do, just wanted to get my first post out there!