Hello,
An enterprise geodatabase reader interprets a value in a date field as: 20130426000000
A file geodatabase reader interprets the same date value as: 20130426
This is a problem when comparing date values in ChangeDetector, as they are always noted as an update, even though they are essentially the same value.
Does anyone have any ideas on how to make the 2 dates comparable?
Best answer by sparki
View original