http://blogs.msdn.com/chrisnorman/default.aspxenCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/chrisnorman/archive/2006/12/19/groove-forms-and-groove-infopath-forms-part-3-which-tool-should-i-use.aspxTue, 19 Dec 2006 15:37:45 GMT91d46819-8472-40ad-a661-2c78acb4018c:1324658Chris Norman7http://blogs.msdn.com/chrisnorman/comments/1324658.aspxhttp://blogs.msdn.com/chrisnorman/commentrss.aspx?PostID=1324658Part 1 of the series is here. Part 2 of the series is here. In past posts, I've outlined some of the differences between the Groove Forms tool and the Groove InfoPath Forms tool. Armed with that background, we can begin to see the criteria to use when...(<a href="http://blogs.msdn.com/chrisnorman/archive/2006/12/19/groove-forms-and-groove-infopath-forms-part-3-which-tool-should-i-use.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=1324658" width="1" height="1">http://blogs.msdn.com/chrisnorman/archive/2006/11/26/groove-forms-and-groove-infopath-forms-part-2-infopath-solution-requirements.aspxSun, 26 Nov 2006 21:19:01 GMT91d46819-8472-40ad-a661-2c78acb4018c:1154559Chris Norman1http://blogs.msdn.com/chrisnorman/comments/1154559.aspxhttp://blogs.msdn.com/chrisnorman/commentrss.aspx?PostID=1154559Part 1 of the series is here . I want to talk about some of the constrains and requirements that Groove has when using InfoPath. There is one point of potential confusion that is worth addressing up front though, which is the use of the term "view". In...(<a href="http://blogs.msdn.com/chrisnorman/archive/2006/11/26/groove-forms-and-groove-infopath-forms-part-2-infopath-solution-requirements.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=1154559" width="1" height="1">http://blogs.msdn.com/chrisnorman/archive/2006/11/16/groove-forms-and-groove-infopath-forms-part-1-data-storage.aspxThu, 16 Nov 2006 23:38:05 GMT91d46819-8472-40ad-a661-2c78acb4018c:1088626Chris Norman1http://blogs.msdn.com/chrisnorman/comments/1088626.aspxhttp://blogs.msdn.com/chrisnorman/commentrss.aspx?PostID=1088626I've had a few conversations lately with solutions developers about the Groove InfoPath Forms tool, and one of the first questions that comes up is how to decide when to use the Groove Forms tool and when to use the InfoPath Forms tool. In order to understand...(<a href="http://blogs.msdn.com/chrisnorman/archive/2006/11/16/groove-forms-and-groove-infopath-forms-part-1-data-storage.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=1088626" width="1" height="1">http://blogs.msdn.com/chrisnorman/archive/2006/10/22/groove-for-developers.aspxMon, 23 Oct 2006 00:05:41 GMT91d46819-8472-40ad-a661-2c78acb4018c:857279Chris Norman2http://blogs.msdn.com/chrisnorman/comments/857279.aspxhttp://blogs.msdn.com/chrisnorman/commentrss.aspx?PostID=857279My name is Chris Norman, and I'm a dev lead on the Groove team. I've been working on Groove for almost 6 years, and have mostly focused on the Groove APIs, the SDKs, and extensibility. I'm currently working on the Groove Forms tool, the Groove InfoPath...(<a href="http://blogs.msdn.com/chrisnorman/archive/2006/10/22/groove-for-developers.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=857279" width="1" height="1">