Ran into problem with grid display of time value. Appears time value is being saved properly, however default DataFormatString generates a string formatting error. I believe the issue is with this line of code:

MyBase.SetStylesAndFormats(Column, CStrN(Format, "{0:t}"))

Format string is passed back to base class which interprets this as a custom format producing erroneous format string: {0:{0:t}}.  As an aside I ran into odd incompatability between .Net and Sql with regard to datetime.minvalue (.net is 0001 and sql is 1753). Anyone attempting to map UDT data back to data typed Sql table will need to adjust time values.

Hi Stefan,

If this is only your first reported bug, it is testament to what a great job and you did with the 3.4 release--congrats.

You may have noticed I posted in this forum recently about a hack I made to your UDT 3.4 code to interface directly to sql tables. I understand why you would not want to encourage this, but for those of us hosting our own DNN apps it can be helpful--my users wanted to be able to also use MS Access to report and interact with UDT data. If anyone is interested I had been using a crosstab query in Access to provide read only access to UDT formatted data.

-Lauren