title: UI Design of WinForm CRUD App, What works?
body: <p>I am designing a WinForms CRUD "like" app for a large group of Nurses and Social Workers to interact with Client information.  </p>
  
  <p>There are many different forms(about <strong>30</strong>ish) that they need to "possiblly" interact with for any given client and they "can be" required to jump from one to another for a specific person.  </p>
  
  <p>I am strugghling with the design of the user interface.  I have only designed very simple linear WEBForm CRUDs where you do what you need on a page and click next.</p>
  
  <p>What makes the mont sense for a non-linear WINForm CRUD app?  </p>
  
  <p>I had started down the path of tabs with embedded forms in those tabs but, possibly due to my lack of ability, the program feels very bulky.  I am not sure straight MDI is the way to go as I have very simple users who may be confused easily if windows are "hidden."  </p>
  
  <p>I would GREATLY appreciate any advice, insight, or examples anyone might have.  Espeacially if anyone has had to make a WINForm CRUD app themselves.  </p>
  
  <p>What UI layout worked(or didn't) for you?  </p>
  
  <p>An example of what mine currently looks like is here --></p>
  
  <p><a href="https://i.stack.imgur.com/451Sr.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/451Sr.jpg" alt=""></a>  </p>
  
  <p>From <a href="http://picasaweb.google.com/TheSchallers/DevFiles?feat=embedwebsite" rel="nofollow noreferrer">DevFiles</a></p>