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/6285.aspxWed, 27 Oct 2004 01:20:50 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:6285Greg Collins0https://www.infopathdev.com:443/forums/thread/6285.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=6285It really depends on your backend storage solution. If you are storing each "record" as a separate form, then you might as well just find a convenient way for the user to load the appropraite form. If all you records are stored in a single .xml file or as a database, it would likely make more sense to have a multi view single form.<br /><br />But these are general recommendations and may not be best suited for your particular requirements.<br /><br />Greg Collins [InfoPath MVP]https://www.infopathdev.com:443/forums/thread/4484.aspxTue, 26 Oct 2004 15:42:01 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:4484jonbrave0https://www.infopathdev.com:443/forums/thread/4484.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=4484Just a question about how one might best approach a simple situation:<br /><br />I have a common (I imagine) requirement. I want an "add new record" form, an "update existing" form, and maybe (not sure) a find/navigate form. Would this be best tackled as a single form with different views, or separate forms (with either links in IP to switch between forms, or just get user to open appropriate form in first place).<br /><br />I'm not sure why, but I'm actually leaning toward separate forms. I'm worried that single form multi-view will end up with lots of code and maybe square peg in round hole... Doubtless either way I'll wish I'd made the opposite decision :)