23:00:00 - with seconds and without double quotes - imports as a date/time field. Change the field to be 'time' and then save the model for future use. There may be other ways but this seems to provide the end result you are looking for.
Double quotes always imply text fields.
If you were extracting from a report, a simple 23:00 would be recognised as a time field.
Separator must be a colon.
Hope this helps. Tell us if not.
Is there a time format in a CSV file that Monarch will recognize without having to do a CTOD() conversion on? I have control over the formating of the time fields in a CSV dump and would like to bring this field, separate from the date field, into to Monarch in such a way that no conversion via a Monarch function is necessary. The time field is surrounded by double quotes. /b[/quote]