InfoPath Dev

Just a question about how one might best approach a simple situation:

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).

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 :)

It 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.

But these are general recommendations and may not be best suited for your particular requirements.

Greg Collins [InfoPath MVP]