M
Michael J Davis
For years we have been generating tables in Visual FoxPro version 3.0b
exporting them as dBase IV files (Type FOX2 = DBase format) so that they
may be imported into Access (in this case ver 2000). (System is
Win98SE).
In the last few days we have had (from a database comprising 10 tables),
three refused by Access, - get external data - we navigate to the folder
in which the file is located, double click on the file and get this
message:-
"The Microsoft Jet database engine could not find the object
'tqibrix23.DBF'. Make sure the object exists and that you spell its
name and the path name correctly."
.... while another 7 from the same folder are imported successfully as
dBase IV files in exactly the same way.
All tables comprise a mixture of character / numeric and logical fields
and I cannot see any significant differences between them.
One of those that cannot[1] be imported has the following structure:
Structure for table: TQIbrix23.dbf
Field Name Type Width
1 ID Num 8
2 WBREF Chr 8
3 BRIX Log 1
4 BLOX Log 1
5 ISO9000 Chr 4
6 ISO9000_CN Chr 26
7 ASSESSOR Chr 12
8 BS3921 Log 1
9 BS3921_CN Chr 12
10 BS6073 Log 1
11 BS6073_CN Chr 12
12 BS6457 Log 1
13 BS6457_CN Chr 12
14 BS6717 Log 1
15 BS6717_CN Chr 8
16 COMMENT Chr 60
17 NOTES Chr 60
18 CONTROL Chr 10
[1] By exporting as TYPE XL5 and then importing into Access as Excel
file, it seems to go smoothly, but this is an unnecessary step.
Can anyone suggest what we are doing wrong, or throw any light on this
problem, please?
Mike
[also posted to comp.databases.xbase.fox]
--
Michael J Davis
Personal email replies may be made to (e-mail address removed)
<><
To earn the right to complain
ensure you are lavish with your praise.
<><
exporting them as dBase IV files (Type FOX2 = DBase format) so that they
may be imported into Access (in this case ver 2000). (System is
Win98SE).
In the last few days we have had (from a database comprising 10 tables),
three refused by Access, - get external data - we navigate to the folder
in which the file is located, double click on the file and get this
message:-
"The Microsoft Jet database engine could not find the object
'tqibrix23.DBF'. Make sure the object exists and that you spell its
name and the path name correctly."
.... while another 7 from the same folder are imported successfully as
dBase IV files in exactly the same way.
All tables comprise a mixture of character / numeric and logical fields
and I cannot see any significant differences between them.
One of those that cannot[1] be imported has the following structure:
Structure for table: TQIbrix23.dbf
Field Name Type Width
1 ID Num 8
2 WBREF Chr 8
3 BRIX Log 1
4 BLOX Log 1
5 ISO9000 Chr 4
6 ISO9000_CN Chr 26
7 ASSESSOR Chr 12
8 BS3921 Log 1
9 BS3921_CN Chr 12
10 BS6073 Log 1
11 BS6073_CN Chr 12
12 BS6457 Log 1
13 BS6457_CN Chr 12
14 BS6717 Log 1
15 BS6717_CN Chr 8
16 COMMENT Chr 60
17 NOTES Chr 60
18 CONTROL Chr 10
[1] By exporting as TYPE XL5 and then importing into Access as Excel
file, it seems to go smoothly, but this is an unnecessary step.
Can anyone suggest what we are doing wrong, or throw any light on this
problem, please?
Mike
[also posted to comp.databases.xbase.fox]
--
Michael J Davis
Personal email replies may be made to (e-mail address removed)
<><
To earn the right to complain
ensure you are lavish with your praise.
<><