Re: field def problem when importing from Excel
- From: Jamie Collins <jamieuka@xxxxxxxxxxxxxx>
- Date: Wed, 03 Oct 2007 03:41:32 -0700
On Oct 1, 10:33 pm, "Keith G Hicks" <k...@xxxxxxxxxxx> wrote:
I read this webpage:http://dailydoseofexcel.com/archives/2004/06/03/external-data-mixed-d...
es/
And my setting is hex 19 (decimal25). Which makes no sense becausehttp://support.microsoft.com/kb/189897says it cannot be higher than 16.
I don't see what this will do to solve my problem anyway. All that should do
is to tell Access to scan 25 rows instead of 19.
I think the KB articles means that 16 is the considered maximum e.g.
you can specify a higher value but it won't be honoured. I suggest you
change the value to zero, which should result in *all* rows being
scanned.
Jamie.
--
.
- References:
- field def problem when importing from Excel
- From: Keith G Hicks
- Re: field def problem when importing from Excel
- From: Pieter Wijnen
- Re: field def problem when importing from Excel
- From: Keith G Hicks
- field def problem when importing from Excel
- Prev by Date: Any way to export a word doc attachment to an access 2003 database
- Next by Date: Re: How do I export large query results?
- Previous by thread: Re: field def problem when importing from Excel
- Next by thread: Re: I'm trying to import an Excel spreadsheet into an exsiting tab
- Index(es):
Relevant Pages
|