For years we have been generating tables in VFP version 3.0b exporting
them as dBase IV files (Type FOX2) 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, while another 7 are imported successfully as
dBase IV files.

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: TQIbrikxx.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
--
Michael J Davis

<><
To earn the right to complain
ensure you are lavish with your praise.
<><

On Tue, 29 Mar 2005 15:11:59 +0100, Michael J Davis
<miked (AT) trustsof (DOT) demon.co.uk> wrote:

I would check if any of the field names are reserved words in Access.
--
[ When replying, remove *'s from address ]
Alexandre Peshansky, Systems Manager, RUH, NY

Alexandre Peshansky <alex*@*mail.rockefeller.edu> opined
Thanks. I will. I have difficulty as the only words in the above list
that seem likely have been used in other tables with no problems.
(Comment, notes, control).

Mike
[The reply-to address is valid for 30 days from this posting]
--
Michael J Davis
http://www.trustsof.demon.co.uk
<><
For this is what the Lord has said to me,
"Go and post a Watchman and let
him report what he sees." Isa 21:6
<><