Hey,
I'm no expert, but I think that if the data is getting "misunderstood"
by Access, you probably have a literal string (probably composed of
alpha-numeric characters) and the string has a leading number (a
number is the first character). I've had a similar issue and I
noticed that if Access is expecting a number, there will be issues
with anything that is not numeric data.
I noticed this when I'd be loading a spreadsheet into Access to
compare. The spreadsheet had a list of clients, but some were new
participants (via the Net) and some were existing clients. The new
clients would have a temporary client ID that would be converted.
However, their temporary ID would begin with a "t" to indicate the
type of client and what we can expect. Here's an example (albeit a
short one) of a list:
102340
134567
t3375
Above are the client IDs. Now since Access is expecting a number, it
will have some funky stuff happen when it gets to the "t3375" and I
believe (I've forgotten, to be honest) that it will chop off the data
and then put it into an "import errors" table within the database.
One way to get around this is to have two separate tables for your
data (one table is numbers only and one table is alpha-numeric) as
Access will interpret one table as having all numbers in that column
and the other table will have a string of alpha-numeric characters.
Well, I know I haven't given too much help, but I think this will
point you in the right direction and you can further research this.
Let me know what turns up.
Cheers!
The Beantown Dude
On Jul 28, 11:59 am, "tina" <nos...@address.comwrote:
i don't have an answer for you, Earl, but i'm interested in the outcome,
too. if you don't get a useful response (or get a thread going) by the end
of the day, suggest you repost your question to
microsoft.public.access.externaldata newsgroup. folks with more expertise
lurk there, including MVP John Nurick; so you may get the help you need.
hth
"Earl Anderson" <isob...@optonline.netwrote in message
news:ez*************@newsfe12.lga...
I guess I missed the boat on the logic for this one. Immediately upon
hitting "Import" in an
attempt to import an Excel file containing 7 columns of 'txt' formatted
data
into AXP, I got a "Type mismatch" error. A search of previous posts
indicated that Access did not 'like' most data types being imported except
for 'txt' files, so I saved the 'xls' as 'txt' and that didn't work
either,
receiving the same "mismatch" error message. (Crudely, I can always 'cut
&
paste' my data into a table I guess).
My question is if there is a "Type mismatch" on a truly text
data type, converted 'xls' file, what is Access 'matching' the data type
against since
no table (and therefore no data & structure) was ever presented as the
import destination? How can something be 'mismatched' if there is nothing
(presented) to 'match' it against?
Thx...
Earl- Hide quoted text -
- Show quoted text -
