https://www.infopathdev.com:443/forums/41.aspxIf you're not sure where to ask your question, ask it here. If necessary, our moderators will make sure it gets classified in the correct board.enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/11334.aspxMon, 19 Mar 2007 23:45:04 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:11334Matt Faus0https://www.infopathdev.com:443/forums/thread/11334.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=11334We haven't done my Design Documents for InfoPath forms, but we have done user manual documentation. The reason there is generally not much design document for a Form is because it is so data-based. The only thing that needs to get documented is the Schema and that is done with the Data Source task pane. On top of this, everything is just action event listeners which when commented correctly should usually explain themselves. For forms we normally have a Specification document and then just look at the code and schema for the form itself.<br /><br />https://www.infopathdev.com:443/forums/thread/6133.aspxMon, 19 Mar 2007 14:39:14 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:6133havers_in_va0https://www.infopathdev.com:443/forums/thread/6133.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=6133I know that documentation is generally the last thing on a developers mind but has anyone developed a Detailed Design Document for documenting how your InfoPath forms are designed?