Text Import: The Microsoft Jet database engine could not find the object

  • Thread starter Thread starter Anthony Bollinger
  • Start date Start date
A

Anthony Bollinger

I am trying to import a fixed-length text file into a new, blank MS Access
database. I am on Win XP sp2 using Access 2003 and the database it created
is version 2000. When I import, I get the error message in the subject line
and right after "object" are two single quotes with nothing between them.
As I have researched this issue, it seems a file name should be there. My
text file was not in 8.3 format, but I renamed it to be TL59a.txt, so that
is not the cause after all.

Strangest thing is I can link to the text file, but not import it. Go
figure, but anyway, this is a bug. Anyone found the fix or workaround?

Thanks!
Tony
 
Hi, Anthony.
My text file was not in 8.3 format, but I renamed it to be TL59a.txt, so
that is not the cause after all.
Click to expand...

Did you apply the same rule to the path? How many feet long is the path
name?
Strangest thing is I can link to the text file, but not import it.
Click to expand...

Can you import other text files, just not this one? If so, can you import
this file if you move the file to the root directory of your C:\ drive?
(And hence, use the shortest path name possible.)

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
 
'69 Camaro said:
Did you apply the same rule to the path? How many feet long is the path
name?


Can you import other text files, just not this one? If so, can you import
this file if you move the file to the root directory of your C:\ drive?
(And hence, use the shortest path name possible.)
Click to expand...

I had thought about the path, but not tried it. OK, now I tried it an it
does not import from the root of my drive. Also, I get the same error with
other text files. I have saved the specs so I don't have to reenter them
every time. Although this could be a factor, I don't think so. If you
enter the specs with any inconsistencies, Access picks up on it. All of the
specified fields, about two dozen, are text, so there should be no issue
there.

Thanks for any further suggestions,
Tony
 
Mystery solved. I shouldn't be surprised that the error message is cryptic.
Through process of elimination, I found that the import specs utility
doesn't check as carefully as I had assumed. I lumped the last block of the
record I was importing into one text field, since I didn't need it except to
re-export when done, but the length was 806. Rather than Access catching
the simple error, and rather than me thinking to make it a memo, I was
getting the above message, totally unrelated. Now it imports fine.

Incidentally, I don't know anything about machine code or debugging, but I
launched the debugger on it and it said it was an unhandled exception, which
must be the reason it blew out to the generic but irrelevant error message.

Thanks,
Tony
 
Back
Top