Wouldn't it be
ds.Rate[0].NineMonthRate
>To all who don't use strongly-typed datasets, I highly recommend them. They aren't that difficult once you figure out how to use them correctly, and there are many advantages.Indeed. Totally agree.
Just finishing work on a very complex C#2.0 web app that I inherited 80% complete. Had to fit the additions and bug fixes within the original design. Physical 3-Tier, very OOP, using web services all over the place to jump through tiers. The guy returns complex collections within collections, within collections (in some cases up to 5 levels deep), instead of datasets. The typed datasets are handled at the DAL, calling SQL Server Stored Procedures that returned in many cases up to 5 different result sets. Then the DAL converts (using foreach), every single row into an element in a collection (e.g. a collection of Modules, has a collection of Levels, that contains a collection of Questions, that contains a collection of possible Answers - it's a questionnaire creation program with multiple choice answers - then a collection of recommendations on each possible answer).
Drove me crazy to follow the logic. Without step-by-step debugging and Intellisense I could not have figured his program out.
