InfoPath Dev

Hi all, At this time i want creat a group of cascading dropdown lists in a browse forms, i can see there are some methods through by writing code,but because of the requirement i need to perform this without writing code. Can some one give me any advice? Thanks.   Best Regards, Eleanore

That is not best practice and probably will effect performance. Plus it is a real nightmare to create and manage the form. If you need some assistance with architecture drop me an email and we can discuss.

I am not sure I know what search terms to use to find the blogs on the subject.  Is there a limit on the number of rules?  I am assuming that the more rules you have the slower the form?  I need to accomplish the same thing and thought that I could get RepeatingSection[@NodeCount]/my:Field1 where @NodeCount is the count of the node ...

Cool interesting areas I can see after 4 days digging in the product is  1) Support for more fancy UI things like adding Ajax, Silverlight or WPF components, compare Silverlight for Sharepoint...  2) The Business logic concept  3) Future: Will InfoPath meet Entity Framework or where will InfoPath be in the Astoria(Oslo ...

I will be at the MVP conference next week and meeting with the InfoPath team so maybe I will have some information after that which I can disclose.

TCO is important and easy to create the next form.... MOSS will be a key coimponent and I like what I have seen with Document Information panels etc... It would be nice to see where the next version of InfoPath will go... I was at ODC2008 in SF and didn't see any stories about InfoPath and the future...

The big advantage of using InfoPath for development is that normal users can then design and manage their own forms without dependencies on developers.  Leveraging the built in features each successive from can leverage a lot of the last one.  Most of what I do is codeless so it can be reused and adapted for multiple users.  ...

We have not selected how to create forms yet. Infopath could be one way forward but it looks like we should implement more than 60 processes for external users to initiate ==> means that intenally we will have much more so to have the business rules at one place could be a time saver and a maintenance saver...  I think the Infopath client ...

Random does it mean that the same person gets it or different persons ... I read today a nice chapter in the book "Designing Forms for Microsoft Office InfoPath and Forms Services 2007" http://safari.informit.com/0321410599 and the security set up in InfoPath is not trivial some links to start ...

Are you using browser based forms or the InfoPath client? Typically we use web services to off-load some of the processing and also to standardize our forms. I would be interested in learning your requirements and the scope of what you are wanting to accomplish. It sounds interesting.