Home Page Link
  Skip Navigation Links
<blog/>
Information Worker > Blogs > <blog/> > Posts > When not to use Infopath
When not to use Infopath
 
Pre-sales loves the idea that they can sell IP (InfoPath).  Telling clients that the end users will be able to maintain the applications.
 
In many cases this is correct.
 
However:
1)  If its so easy then why are the end users doing the forms?
1)  Motivation.  Devs don't want to do IP, its not cool
2)  There is some learning involved
 
What happens to code?
 
Famous software engineer Brooks wrote a paper called "No Silver Bullet"
http://en.wikipedia.org/wiki/No_Silver_Bullet
The paper says, inter alia, it will be used in ways that are not intended.
 
Well written software gets used for more than intended.  If the devs start doing Infopath Forms, the forms will inevitably get used for unscalable applications
If we as devs must write systems that use software designed for end users it creates some problems:
1) Parts of it will be in complicated .net code (end users can forget fixing code behind)
2) Unmaintainable, 50 IP forms all calling one another, IP rules, work arounds etc?
3) IP does not scale in the way devs expect
 
 
My rule:
1) Make the end users do it
2) If it would take longer that 2 hours, then code it with the enterprise scale stuff, like asp.net
3) If there are going to be lots of IP forms
4) ANY code behind
 
 
 

Comments

There are no comments yet for this post.

RSS Feed RSS 2.0 Feed



1
1
1
1
Tags
    1
    1
    1
    1


    Feedback