M
MC
Is a Microsoft resource available? Would love to know if the
following behavior is a bug or a feature of Jet 4.0 SP5 or higher --
thanks in advance for your help!
With Acc2000 and Jet 4.0 SP8 installed, attempt to import a Paradox
4.5 table fails with the error "Index or Primary Key cannot contain a
Null value".
The Paradox table doesn't have a primary key defined.
Acc2000 and Jet 4.0 SP3 will import the identical table without error.
KB 230126 states that the ISAM driver for Paradox (mspbde40.dll)
requires that LINKED Paradox tables have a primary key defined, in
order to update the table. The article doesn't place this requirement
on IMPORTED tables. And Access online help (see topic "import and
link data objects") doesn't state that requirement either.
For grins, I imported the same table -- found a primary key placed on
the first 2 fields (both Text, and both had field names that included
one of the AutoIndex strings). And indeed, several records had NULL
values in one of the PK fields. This wouldn't have been a problem,
had Access not forced the PK.
I'd thought that perhaps the import behavior had been influenced by
the AutoIndex property when creating the output table. Perhaps Access
would be inclined to define a 2-field PK on these fields, since it had
also defined a "Duplicates OK" index on them already. So I removed
the string in question from the AutoIndex property -- but import still
tried to force definition of the primary key on these fields.
Is this a new 'feature', or a software problem? If the latter, I can
contact PSS for help.
Thanks!
following behavior is a bug or a feature of Jet 4.0 SP5 or higher --
thanks in advance for your help!
With Acc2000 and Jet 4.0 SP8 installed, attempt to import a Paradox
4.5 table fails with the error "Index or Primary Key cannot contain a
Null value".
The Paradox table doesn't have a primary key defined.
Acc2000 and Jet 4.0 SP3 will import the identical table without error.
KB 230126 states that the ISAM driver for Paradox (mspbde40.dll)
requires that LINKED Paradox tables have a primary key defined, in
order to update the table. The article doesn't place this requirement
on IMPORTED tables. And Access online help (see topic "import and
link data objects") doesn't state that requirement either.
For grins, I imported the same table -- found a primary key placed on
the first 2 fields (both Text, and both had field names that included
one of the AutoIndex strings). And indeed, several records had NULL
values in one of the PK fields. This wouldn't have been a problem,
had Access not forced the PK.
I'd thought that perhaps the import behavior had been influenced by
the AutoIndex property when creating the output table. Perhaps Access
would be inclined to define a 2-field PK on these fields, since it had
also defined a "Duplicates OK" index on them already. So I removed
the string in question from the AutoIndex property -- but import still
tried to force definition of the primary key on these fields.
Is this a new 'feature', or a software problem? If the latter, I can
contact PSS for help.
Thanks!