Since I'm dealing with a lot of data I'm trying to aviod the reflection based hydrators. My tables that have a single integer key are using iHydratable adn that's working fine. For the multiple key tables it's not, as those are done in the controller.

                Using dr As IDataReader = DataProvider.Instance().ListPeaks(portalId)
                    While dr.Read
                        Dim PeakInfo As PeakInfo = New PeakInfo
                        PeakInfo.PeakDate = Convert.ToDateTime(Null.SetNull(dr.Item("PeakDate"), PeakInfo.PeakDate)) <-Charles syntax
                        PeakInfo.PeakDate = Convert.ToDateTime(Null.SetNull(dr.Item("PeakDate")) <- Michael's syntax (both fail)
                       PeakInfo.PeakServiceGroup = Convert.ToString(Null.SetNull(dr.Item("PeakServiceGroup")))
                        PeakInfo.PortalId = Convert.ToInt32(Null.SetNull(dr.Item("PortalId")))
                        PeakInfo.PeakExecutions = Convert.ToInt32(Null.SetNull(dr.Item("PeakExecutions")))
                        PeakInfo.TotalResponse = Convert.ToDecimal(Null.SetNull(dr.Item("TotalResponse")))
                        PeakInfo.PeakResponse = Convert.ToDecimal(Null.SetNull(dr.Item("PeakResponse")))
                        PeakInfolist.Add(PeakInfo)
                    End While

The examples from Charles and Michael differ, I've noted the differences in the conversions for PeakDate. Unfortunately both fail. The format shown in the 2nd example (michaels) works fine in the Info module iHydrator. In the business controller I get the error "Unable to cast object of type 'System.DateTime' to type 'System.Reflection.PropertyInfo'.". I both in need of a solution, and a explanation of the two differnet methods so I can understand what I'm up to.

I am bypassing reflection imtentionally because it is very ineffecient when processing volumes of data. Bypassing reflection is a documented performanec boost, see articles by Charles Nurse and Michael Washington.

In any case fewer lines of code in your programs doesn't mean fewer lines of code executed, which is my point. If you look at CBO reflection there's quite a bit of activity that I need to aviod. My modules aren't dealing with a few hundred rows, but in some cases several thousand and the performance hit from CBO is impractical.

Hi Keith on the top codes, can you declare the object as follow:
Dim objPeakInfo As PeakInfo = New PeakInfo Instead of Dim PeakInfo As PeakInfo = New PeakInfo

See if the code works.