Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I have a number of older spreadsheet applications which use the recordset
GetRows() method to fetch recordset data into a variant array and then use Range("Data").Value = varData() to get the data into Excel. MS KnowledgeBase article: 246335 - "How To Transfer Data from an ADO Recordset to Excel with Automation" gives an example of doing this. It also recommends the newer CopyFromRecordset technique for later versions of Excel. I have many older apps that use the Array technique, which I don't want to re-code at this time. The problem is that in Excel 2003, any date fields are interpreted as American dates (mm/dd/yy) rather than Australian dates (dd/mm/yy) when the data is put into the worksheet by Range("Data").Value = varData() . Excel 2000 did not have the same problem. Has anyone else had this problem, and know of a solution? The newer CopyFromRecordset technique works, but it will mean a lot of re-coding. |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Problem copying a formula in Excel 2003 | Excel Discussion (Misc queries) | |||
problem copying visible cells from 2000 to 2003 | Excel Discussion (Misc queries) | |||
Problem copying ADO recordset to Excel 2003 | Excel Programming | |||
ADODB Recordset problem | Excel Programming | |||
Conceptual Problem with DAO/ADO Recordset | Excel Programming |