Why InfoPath?

Okay, I'm going to try a different approach on the "why do I care about InfoPath?" issue.

 I recorded a short screencast and posted it to Channel9: https://channel9.msdn.com/ShowPost.aspx?PostID=343092 

 In the screencast, I walk through setting up an InfoPath form to connect to a database, and show how the idea is to free up developers from having to write form after form after form...

 I'd like feedback on if this approach helps, and if you'd like to see more screencasts.

For those who are wondering, the last year has been a bit, um, "interesting." I transferred out of my Office Developer role and over to the BI group, was in the BI group when we acquired ProClarity, lived through PerformancePoint's growing pains, and just three months ago transferred again to the Lockheed Martin account team. So - bumpy roads all around.

I'm going to broaden the focus of the blog here a bit (but Philo, how can it be any broader than "haven't posted anything"?) well... I'm going to start covering Business Intelligence as well, but keep a solution-oriented focus including SharePoint and InfoPath.

We'll see how it goes.

Comments (6)

  1. James says:

    I agree but if you add managed code to the infopath form it takes too long to instantiate.   Too long for an application that will used in an enterprise.

  2. Ian says:

    Nice recording Philo.  I feel that more people need to understand use cases of InfoPath, and this was a good example of one.

    I feel the power of InfoPath is that it lets the business create and manage their own forms.  InfoPath can be seen as one of the tools to help them get their job done.

  3. rasx says:

    You probably were not allowed (or just forgot—or I forget) but it would have been useful to compare how this direct connection to the database was done in the InfoPath 2003 time frame. I do not recall granting Full Trust and connecting (without a scary security message) was so easy.

  4. MSDN Archive says:

    "it would have been useful to compare how this direct connection to the database was done in the InfoPath 2003 time frame"

    Yeah, I’ve gotten calls on that, among other aspects of the demo. (Post a quick and dirty demo, get called on it being demoware – can’t win…)

    I’ll post an amplifying article about the security aspect later this week, as well as some other uses of InfoPath and a more complex form.

    That one was just supposed to whet the appetite. 🙂

  5. Body: I've been getting some curly questions around InfoPath of late due to our organisation already

Skip to main content