>>>>>>Interesting naming convention
>>>>>
>>>>>Which?
>>>>>
>>>>>>Your original table has date in character format. When you produce CSV can you change it to date (use CTOD, if you want)?
>>>>>
>>>>>Do you mean IntermTable? That has just been created by importing the XLS. How can I use CTOD() in that process?
>>>>>I had no initial input in the production of the XLS/CSV, but had to reformat it somewhat to get it to feed to this program.
>>>>>
>>>>>Si ... don't understand. Thanks
>>>>>
>>>>
>>>>I guess, I misundertstood you originally. Ok, your intermTable is from Excel, which explains strange names for the fields.
>>>
>>>What strange names? They're just field names as any other.
>>>
>>>>And in your IntermTable dates are in C format, correct?
>>>
>>>Correct - the XLS date field yields a char date field in IntermTable
>>>
>>>>What do you receive when you convert these dates back to date? Of they already come wrong?
>>>
>>>

>>>Replace	Operator	with tnOperator, ;	
>>>         ...
>>>  	Date with CTOD( m.E), ;
>>>         ...
>>>

>>>is in the code (as I posted). This is what yields dd/mm/1920 in the result FB1.DBF
>>>
>>>>
>>>>Thanks.
>>
>>What you have in E field?
>
>Well, a char representation of the date, e.g. "16-06-2006", as the result of the import from XLS.

If I remeber well you do this in FPD, right? What is the result of:

SET DATE BRITIH
SET CENTURY ON ROLLOVER 50  && I am not sure FPD have ROLLOVER option, so remove it if it doesn't exists
SELECT IntermTable
GO 2
? CTOD(ALLTRIM(E))