DBF Import

[Guest]

Hello,

I'm working on an Access application that imports DBF files. When using
Access 2003 (11.5614.5606) it worked fine, but i have since gotten a new
workstation that has Access 2003 (11-6566-8036 SP2) and now when I try to
import a DBF file, whether manually or programmatically, I get the following
error: The Microsoft Jet Database engine could not find the object <name>.
Make sure the object exists and you spell its name and the path name
correctly.

Obviously, I have confirmed that the name and the path is correct, and when
I attempt the import manually, I browse to it anyway, and it gives the same
error. Anyone have any ideas?

Thanks in advance,

Martin Conrad
Systems Engineer
Marshall & Sterling

 

[Guest]

Hi Again,

OK, was this question too stupid to answer, or too difficult?

Thanks again...

 

[John Nurick]

Hi Martin,

Are you certain this isn't the old problem with long file or folder
names?

I'm using Office 2003 SP2, though my copy of Access reports a different
build number, and have just imported data manually from a couple of dbfs
without any problems (except that attempting to import the file
BT01 with a space.DBF
produced "The Microsoft Jet database engine could not file the object
'C:\Documents and Settings\John Nurick\My Documents\BT01 with a
space.DBF'. Make sure the object exists and you spell its name and the
path name correctly." and I had to specify the equivalent short name
BT01WI~1.DBF
).

IIRC there's also an issue with drivers for some versions of the DBF
format being installed or not installed with various versions of Jet. If
you search this group (e.g. at groups.google.com) for posts by Cindy
Winegarden that contain relevant keywords you'll learn more than I can
tell you.

 

[Guest]

Hi John,

Thanks for the reply. Through some experimenting on my own, I found
that the issue was in fact long file names, but this was never an issue with
pre-service pack 2...I have confirmed this by getting out my old system
(which fortunately hasn't been rebuilt yet) and it worked fine. Do you know
what they changed? ...and is there a patch of some sort? This will mean a lot
of revision to a project that we had considered nearly completed...

Thanks.

 

[John Nurick]

Hi Martin,

I don't know the ins and outs of working with .dbfs, I'm afraid. One
possibility is to create a FileSystemObject object and use that to get
the short path that corresponds to your real one. If you search this
newsgroup for a thread starting on 18 Aug 2006, subject
import longfilename.DBF
you'll find some sample code and some other posts that may cast light on
hte problem.