Instead, use a macro or VBA code to do the export, using the
TransferSpreadsheet method. See Help for info on how to set this up.
--
Ken Snell
<MS ACCESS MVP>
"MarcusLesser" <Marcus...@discussions.microsoft.com> wrote in message
news:F0BCBB51-D01D-46BC...@microsoft.com...
On Wed, 17 Nov 2004 08:32:58 -0500, "Ken Snell [MVP]"
<kthsne...@ncoomcastt.renaetl> wrote:
>If you use the manual export (FIle | Export) process, this truncation occurs
>because that process outputs the data using Excel 95 format, which did not
>support character strings over 255 characters long.
>
>Instead, use a macro or VBA code to do the export, using the
>TransferSpreadsheet method. See Help for info on how to set this up.
Please respond to the Newsgroup, so that others may benefit from the exchange.
Peter R. Fletcher
> If you use the manual export (FIle | Export) process, this truncation occurs
> because that process outputs the data using Excel 95 format, which did not
> support character strings over 255 characters long.
>
> Instead, use a macro or VBA code to do the export, using the
> TransferSpreadsheet method.
Another option is to specify Excel 8.0 in a query e.g.
SELECT MyMemoCol
INTO [Excel 8.0;Database=C:\OutFile.xls;].NewExcelTable
FROM MyTable
;
Jamie.
--
I've never run into that approach, which is extremely cute - where is
it documented?
> >Another option is to specify Excel 8.0 in a query e.g.
> >
> > SELECT MyMemoCol
> > INTO [Excel 8.0;Database=C:\OutFile.xls;].NewExcelTable
> > FROM MyTable
> > ;
>
> I've never run into that approach, which is extremely cute - where is
> it documented?
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q295646
How To Transfer Data from ADO Data Source to Excel with ADO
As with many MSDN articles, you have to look beyond the title i.e. the
syntax is odbc pass-through and does not use OLE DB on which ADO is
based.
Jamie.
--