D
David Vardy
We have an SQL table whose fields are all varchar (because
it is used as a temp holding area and the info in it may
be date, number, text etc depending on which report uses
it). This is read in to a recordset by a VB programme,
Excel is opened and the fields copied from the recordset
into the workbook one by one.
However, a date of 01/04/2003 in the SQL tablle appears as
04/01/2003 in the workbook. 14/04/2003 copies across OK
as does any date where the day is over 12.
Can you help us to stop this happening?
The Windows NT Region country settings are correct at UK.
Thanks,
David
it is used as a temp holding area and the info in it may
be date, number, text etc depending on which report uses
it). This is read in to a recordset by a VB programme,
Excel is opened and the fields copied from the recordset
into the workbook one by one.
However, a date of 01/04/2003 in the SQL tablle appears as
04/01/2003 in the workbook. 14/04/2003 copies across OK
as does any date where the day is over 12.
Can you help us to stop this happening?
The Windows NT Region country settings are correct at UK.
Thanks,
David