Problems Linking a DBase4 file to Access2000

  • Thread starter Thread starter Chris Thorne
  • Start date Start date
C

Chris Thorne

When I attempt to link the file, "AuditHist.dbf" to an
Access DB I get the messaage, "The Microsoft Jet Database
engine could not find the object 'AuditHist.dbf'. Make
sure the object exists and that you spell its name and the
path name correctly." I have established from a previous
posting that if the name of the file is truncated to 8.3,
then the link will work. However, to change the filename
of this file is a bit of a nightmare. A colleague who runs
with Windows2000 SP4 and Office2000 SP3, the same as me,
is able to link this file in its current state with no
problems. Does anyone know what my system may be lacking?
Thankyou in advance.
 
Hi Chris,

1) Is the path to the file longer on your machine? I think there's a
64-character limit.

2) Even with the same versions of Windows and Office you could have
ended up with different versions of Jet on the two machines.

3) If the file is immovable and unrenamable and on an NTFS volume, it's
a candidate for a hard link, which is an additional directory entry for
a file. There's a "ln" utility in the POSIX tools in the Windows 2k
resource kit to create them. The link can have a different name and be
in a different folder (but must be on the same volume), so you can give
it a convenient short name and path.
 
I am having the same problem in Access97 except with a
Paradox DB. I did rename it to an 8.3 format and now I
get "External table isn't in the expected format. (Error
3274)".

Mark
-----Original Message-----
Hi Chris,

1) Is the path to the file longer on your machine? I think there's a
64-character limit.

2) Even with the same versions of Windows and Office you could have
ended up with different versions of Jet on the two machines.

3) If the file is immovable and unrenamable and on an NTFS volume, it's
a candidate for a hard link, which is an additional directory entry for
a file. There's a "ln" utility in the POSIX tools in the Windows 2k
resource kit to create them. The link can have a different name and be
in a different folder (but must be on the same volume), so you can give
it a convenient short name and path.


When I attempt to link the file, "AuditHist.dbf" to an
Access DB I get the messaage, "The Microsoft Jet Database
engine could not find the object 'AuditHist.dbf'. Make
sure the object exists and that you spell its name and the
path name correctly." I have established from a previous
posting that if the name of the file is truncated to 8.3,
then the link will work. However, to change the filename
of this file is a bit of a nightmare. A colleague who runs
with Windows2000 SP4 and Office2000 SP3, the same as me,
is able to link this file in its current state with no
problems. Does anyone know what my system may be lacking?
Thankyou in advance.
Click to expand...

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.
Click to expand...
 
Hi Mark,

I don't have any experience with Paradox (not since 1987, anyway<g>).
All I can suggest is searching the Microsoft knowledgebase.


I am having the same problem in Access97 except with a
Paradox DB. I did rename it to an 8.3 format and now I
get "External table isn't in the expected format. (Error
3274)".

Mark
-----Original Message-----
Hi Chris,

1) Is the path to the file longer on your machine? I think there's a
64-character limit.

2) Even with the same versions of Windows and Office you could have
ended up with different versions of Jet on the two machines.

3) If the file is immovable and unrenamable and on an NTFS volume, it's
a candidate for a hard link, which is an additional directory entry for
a file. There's a "ln" utility in the POSIX tools in the Windows 2k
resource kit to create them. The link can have a different name and be
in a different folder (but must be on the same volume), so you can give
it a convenient short name and path.


When I attempt to link the file, "AuditHist.dbf" to an
Access DB I get the messaage, "The Microsoft Jet Database
engine could not find the object 'AuditHist.dbf'. Make
sure the object exists and that you spell its name and the
path name correctly." I have established from a previous
posting that if the name of the file is truncated to 8.3,
then the link will work. However, to change the filename
of this file is a bit of a nightmare. A colleague who runs
with Windows2000 SP4 and Office2000 SP3, the same as me,
is able to link this file in its current state with no
problems. Does anyone know what my system may be lacking?
Thankyou in advance.
Click to expand...

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.
Click to expand...
Click to expand...
 
Thanks everyone for your help. I have since written code
to copy the DBase4 file and change its name to a 8.3
character filename. But this still doesn't explain why my
colleague's computer has no problem in reading the file,
yet mine can't. I loaded MSJet4.0 SP8 but there has been
no change - I still can't link the file when it's got 9
characters in the filename.
-----Original Message-----
Hi Mark,

I don't have any experience with Paradox (not since 1987,
Click to expand...
anyway said:
All I can suggest is searching the Microsoft knowledgebase.
I am having the same problem in Access97 except with a
Paradox DB. I did rename it to an 8.3 format and now I
get "External table isn't in the expected format. (Error
3274)".

Mark
-----Original Message-----
Hi Chris,

1) Is the path to the file longer on your machine? I think there's a
64-character limit.

2) Even with the same versions of Windows and Office
Click to expand...
you
could have
ended up with different versions of Jet on the two machines.

3) If the file is immovable and unrenamable and on an NTFS volume, it's
a candidate for a hard link, which is an additional directory entry for
a file. There's a "ln" utility in the POSIX tools in
Click to expand...
the
Windows 2k
resource kit to create them. The link can have a different name and be
in a different folder (but must be on the same volume), so you can give
it a convenient short name and path.


On Thu, 11 Dec 2003 18:42:29 -0800, "Chris Thorne"

When I attempt to link the file, "AuditHist.dbf" to an
Access DB I get the messaage, "The Microsoft Jet Database
engine could not find the object 'AuditHist.dbf'. Make
sure the object exists and that you spell its name and the
path name correctly." I have established from a previous
posting that if the name of the file is truncated to 8.3,
then the link will work. However, to change the filename
of this file is a bit of a nightmare. A colleague who runs
with Windows2000 SP4 and Office2000 SP3, the same as me,
is able to link this file in its current state with no
problems. Does anyone know what my system may be lacking?
Thankyou in advance.

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.
Click to expand...
Click to expand...

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.
Click to expand...
 
Back
Top