problem with acess driver?

  • Thread starter Thread starter jim
  • Start date Start date
J

jim

I have a program that gathers prices yearly from a data
disc, and while updating the prices using the Windows XP
operating system at the end of the importation I receive
this error.

Microsoft[ODBC Microsoft Access Driver] Index or primary
Key cannot contain a null value.

Now I'm not using Access, and I'm not sure if there is
any relation to the Access program, but I figured it
might have something to do with it.

Any suggestions

Thank you,

Jim
 
It is a misnomer, really. Technically, it should be
called [ODBC Microsoft JET Driver].

JET is the default database engine used by Microsoft
Access since Access version 1.0. Since Access is more
well-known, Microsoft decided to call the ODBC driver
[ODBC Microsoft Access Driver] and hence the confusion.

Both have been upgraded numerous times (Access 2003 uses
JET 4.0). Note also that Access can use other database
engines, not just JET.

HTH
Van T. Dinh
MVP (Access)
 
There is something wrong with your data: possibly just
a bad record at the end, or perhaps the data disk doesn't
match your program at all. The message is telling you
that (at least part of) the import failed because the
data couldn't be loaded correctly into a table.

(david)
 
Hello Van,

Trouble is when this pops up, it will not allow the data
importation. Is there a way to correct this problem?

Thanks,

Jim
-----Original Message-----
It is a misnomer, really. Technically, it should be
called [ODBC Microsoft JET Driver].

JET is the default database engine used by Microsoft
Access since Access version 1.0. Since Access is more
well-known, Microsoft decided to call the ODBC driver
[ODBC Microsoft Access Driver] and hence the confusion.

Both have been upgraded numerous times (Access 2003 uses
JET 4.0). Note also that Access can use other database
engines, not just JET.

HTH
Van T. Dinh
MVP (Access)


-----Original Message-----
I have a program that gathers prices yearly from a data
disc, and while updating the prices using the Windows XP
operating system at the end of the importation I receive
this error.

Microsoft[ODBC Microsoft Access Driver] Index or primary
Key cannot contain a null value.

Now I'm not using Access, and I'm not sure if there is
any relation to the Access program, but I figured it
might have something to do with it.

Any suggestions

Thank you,

Jim
.
Click to expand...
.
Click to expand...
 
Have you checked the data being imported into the JET Tables?

It sounds like you importing data into Fields that are either PrimaryKey (a
unique non-Null value is required for eah Record / row) or Null is not
allowed and some of the rows being imported don't have values for these
Fields.
 
You have to look at your Table Design and see which Field is the PK or any
Field that Null is not allowed and check the source data for corresponding
values.
 
Back
Top