InfoPath Dev

Hello there, i am more or less new in the area of InfoPath (and SharePoint 2007) Coding. Until yet i have prevent using CodeBehind in InfoPath, also because i was be able to realize all functionality i need without CodeBehind. But i encountered one Problem a couple of days ago which couldnt be solved without code: http://social.msdn.microsoft.com/Forums/en-US/sharepointinfopath/thread/ac9faa08-5bd7-45f2-9714-16eec23d8181 Actually, i am worried about the decision to try it out with code. So i wanted ask this wonderful community as long as i have a change to go back - what are the nagtive aspects of CodeBehind in InfoPath? Maybe there are some which i dont know, and to be honest, except own failures which could be in a Code, i cant imagine any other "negative" parts of CodeBehind. Links to other Threads or Pages are welcome too, i will read them all :)

It requires more overhead, requires a developer to maintain it, requires Visual Studio, requires Full Trust, requires administrative approval, and requires uploading to Central Admin, which requires MOSS Enterprise.

Okay ^^ thanks for the answer.

To complete this list:

AND require installed .NET 2.0 Framework on the Client, AND InfoPath .NET CodingSupport Installation (a feature you can add/remove over the custom office Installation)