I have run into this before and it is really a pain to workaround. WHat
happens is that excel has that column formated as a "general" column. I
believe if the sheet had the column format as a "TEXT" format then this
would help. Otherwise, the ODBC drivers look at the first row of data
and ASSUME the rest of the column is that data type.
So try and see if you can get the spreadsheet saved with that column
listed as a text format. If you cannot do this then you will need to
create an import spec that allows you to import the data in to an Access
DB, then call Access from the cmd line (could use a CF_ tag for this)
to imvoke a defined macro that will cause the import to take place.
Doable, but a real pain.
Steve
-------- from an email last year that I sent to the list --------------
How about using access's File Import directly, with a start up macro
so that ACCESS will do the import automagically?? You could even use
a "import special" mdb that really has a link to the real mdb you want
to import into. From MSA97:
You can use a special macro named AutoExec to carry out an action or series
of actions when your database first opens. When you open a database,
Microsoft Access looks for a macro with this name and, if it finds one,
runs it automatically.
1 Create a macro containing the actions you want to run when you open the
database.
How?
2 Save the macro with the name AutoExec.
The next time you open the database, Microsoft Access runs this macro
automatically.
Notes
� If you don't want to run the AutoExec macro when you open the database,
hold down the SHIFT key when the database opens.
� You can also control how a database or application starts by setting
options in the Startup dialog box (Tools menu).
At 06:18 PM 4/28/2000 +0100, Philip Arnold - ASP wrote:
>It's been a long time since I've been on this list, but I've run into a
>problem that someone here might have some insight into...
>
>I'm using an Excel ODBC datasource (as that's how the client supplies 3Mb of
>data), but the same problem arises if I make it as a Link Table in Access,
>or even as a CSV datasource
>
>Two of the columns are telephone numbers, but when ODBC reads it, it treats
>it as a numeric, which means that any entries which have spaces in are
>ignored - as they aren't truly numeric, e.g. 0015124267712001 works (as
>15124267712), but 001 512 426 7712 is ignored.
>
>I know it's something in the Excel connector, but I'm hoping I can solve
>this.
>
>I'm running MDAC 2.1 SP2 (is 2.5 worth the upgrade?) and CF 4.01 (I know I
>should run my upgrade to 4.51, but I haven't had the chance yet)
>
>I hope someone can help me with this, as I'm tearing my hair out (what
>little I have left)
>
>TIA
>
>Philip Arnold
>ASP Multimedia Limited
>T: +44 (0)20 8680 1133
>
>"Websites for the real world"
>
>**********************************************************************
>This email and any files transmitted with it are confidential and
>intended solely for the use of the individual or entity to whom they
>are addressed. If you have received this email in error please notify
>the system manager.
>**********************************************************************
>
>
>---------------------------------------------------------------------------
---
>Archives: http://www.eGroups.com/list/cf-talk
>To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
>
--
Stephen Garrett
GPS
[EMAIL PROTECTED] (360) 896-2714
ICQ# 10776767
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebarRsts&bodyRsts/cf_talk or send a message
to [EMAIL PROTECTED] with 'unsubscribe' in the body.
