UltraCalendarCombo back to the 1930s

Answered (Verified) This post has 1 verified answer | 3 Replies | 2 Followers Thread's RSS feed.

schaffnerc
Points 125
Replied On: Tue, Feb 28 2012 9:33 AM Reply

Inputting a Date in the format dd/mm/yy causes a fault if data is later than 2029: Inputting "30/11/30" creates the wrong Date "30/11/1930". But Inputting 30/11/29 creates a Date like "30/11/2029" correct.

What do I need to do to stay in the 21 Century ;-) ?

  • Post Points: 35

Verified Answer

Answered (Verified) Replied On: Mon, Mar 5 2012 4:08 PM Reply
Verified by schaffnerc

Hi schaffnerc,

Parsing of the DateTime object is executed by the .NET framework and the behavior can be adjusted from within the Windows 7 Control Panel’s Region and Language settings. From the Region and Language menu, select “Additional Settings” and then select the “Date” tab. Under the Calendar group, you may adjust the parameters used when interpreting a two digit year.

 

By default, the cutoff date is set to 2029; however, you may adjust this date to obtain the desired range or you can override the parsing behavior programmatically.

I have constructed and attached a sample which demonstrates a programmatic approach with the ultraCalendarCombo, just in case you are interested in that route.

Please find the sample attached.

If you have any questions at all regarding these solutions, please let me know.

Sincerely,
Chris K
Developer Support Engineer
Infragistics, Inc.
www.infragistics.com/support

  • Post Points: 25

All Replies

Answered (Verified) Replied On: Mon, Mar 5 2012 4:08 PM Reply
Verified by schaffnerc

Hi schaffnerc,

Parsing of the DateTime object is executed by the .NET framework and the behavior can be adjusted from within the Windows 7 Control Panel’s Region and Language settings. From the Region and Language menu, select “Additional Settings” and then select the “Date” tab. Under the Calendar group, you may adjust the parameters used when interpreting a two digit year.

 

By default, the cutoff date is set to 2029; however, you may adjust this date to obtain the desired range or you can override the parsing behavior programmatically.

I have constructed and attached a sample which demonstrates a programmatic approach with the ultraCalendarCombo, just in case you are interested in that route.

Please find the sample attached.

If you have any questions at all regarding these solutions, please let me know.

Sincerely,
Chris K
Developer Support Engineer
Infragistics, Inc.
www.infragistics.com/support

  • Post Points: 25
Replied On: Thu, Mar 8 2012 4:08 PM Reply

Hi schaffnerc,

If I may be of any further assistance regarding this inquiry, please let me know.

Sincerely,
Chris K
Developer Support Engineer
Infragistics, Inc.
www.infragistics.com/support

  • Post Points: 20
schaffnerc
Points 125
Replied On: Tue, Mar 20 2012 9:26 AM Reply

Hi Chris,

this solved my problem. I'll ask the users to change their settings as we have to many regional settings like dd.mm.yyyy, dd/mm/yyyy, mm.dd.yyyy or mm/dd/yyyy.

Thank you and Regards,

Chris S

 

  • Post Points: 5
Page 1 of 1 (4 items) | RSS