[BUG] Editing Dates

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hi there,
There appears to be a bug for machines that have a regional date setting of a single month format. So, a customer has it set to "DD/M/YYYY". To get the PropertyGridItemDate to show the date in this format, you simply set the .Format() property to be be empty (vbNullString).

This works fine and shows the date correctly. However, for one digit months (16/7/2012 for example), when you give focus to the value to edit it, the input mask appears to be a "DD/MM/YYYY" format and it will blank out the month and year values!!!!! It looks very odd and could possibly lead to data corruption if the user isn't clued up about it! If the value isn't edited and you cancel the edit, the old value still remains.

You can re-create this issue easily on the code jock property grid sample if you set the DateItem.Format = "", and set you machine format to be DD/M/YYYY.

Any idea on a fix for this?

Cheers!

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Hemesh Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 10 August 2010 Status: Offline Points: 135	Post Options Post Reply Quote Hemesh Report Post Thanks(0) Quote Reply Topic: [BUG] Editing Dates Posted: 16 July 2012 at 6:28am
	Hi there, There appears to be a bug for machines that have a regional date setting of a single month format. So, a customer has it set to "DD/M/YYYY". To get the PropertyGridItemDate to show the date in this format, you simply set the .Format() property to be be empty (vbNullString). This works fine and shows the date correctly. However, for one digit months (16/7/2012 for example), when you give focus to the value to edit it, the input mask appears to be a "DD/MM/YYYY" format and it will blank out the month and year values!!!!! It looks very odd and could possibly lead to data corruption if the user isn't clued up about it! If the value isn't edited and you cancel the edit, the old value still remains. You can re-create this issue easily on the code jock property grid sample if you set the DateItem.Format = "", and set you machine format to be DD/M/YYYY. Any idea on a fix for this? Cheers!
	Product: Xtreme SuitePro (ActiveX) version 18.5.0 Platform: Windows 7 Enterprise (64-bit) Language: Visual Basic 6.0

Hemesh Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 10 August 2010 Status: Offline Points: 135	Post Options Post Reply Quote Hemesh Report Post Thanks(0) Quote Reply Posted: 21 August 2012 at 3:43am
	Taken with CJ Support Ticket, and it's been fixed for the next release... anyone know when that might be?
	Product: Xtreme SuitePro (ActiveX) version 18.5.0 Platform: Windows 7 Enterprise (64-bit) Language: Visual Basic 6.0

McKloony Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 09 January 2007 Location: Germany Status: Offline Points: 340	Post Options Post Reply Quote McKloony Report Post Thanks(0) Quote Reply Posted: 01 October 2013 at 10:40am
	In 16.2.4 it is not fixed
	Product: Xtreme SuitePro (ActiveX) 16.2.5 Platform: XP / Windows 7 Language: Visual Basic 6.0 SP6