#42 Problem with parsing Date/Time field with milliseconds

[Anonymous]

When defining own log format, I try to use Date/Time date type. If I use format MM/dd/yyyy HH:mm:ss (example log data: 12/12/2012 12:22:11) everything works ok. But right now I have to extend my log file with milliseconds, so right now my log contains entries in format: 12/12/2012 12:22:11.543. If I try to change Gamut format to MM/dd/yyyy HH:mm:ss.fff, I'm getting error: - The date format you entered is invalid.

[Anonymous]

latest version: 2.5.001

[SteveAube]

If you have a log file with two different date formats that will not work. If that is not the case please attach a log, the date format you are trying, the separator character(s) you are using one you are or the Pattern string if you are not.

[Anonymous]

Hi,

I am experiencing the same issue and I believe the reason is that you are trying to change the date/time field in an *existing* configuration. A quick look at the source code shows that it seems that the _input fields from the ConfigColumns are not properly initialized when the dialog is loaded. In my case, I am using Tabs as separators. When I un-select and the select again the tab checkbox for the separators, it suddenly works (at the cost of losing my predefined column headers).

[SteveAube]

Fixed: 03-28-2013 Version 2.5.003 released
- Enahancements:
- Added support for start and end of line separator character strings.
- Bug Fixes:
- 3608165 Problem with parsing Date/Time field with milliseconds when you are trying to change the
date/time field in an *existing* configuration.