ACC2000: dBASE Unique Index Does Not Behave as Expected (199136)
The information in this article applies to:
This article was previously published under Q199136 This
article applies only to a Microsoft Access database (.mdb).
Moderate: Requires basic macro, coding, and interoperability
skills.
SYMPTOMS If you choose a unique field when you link a dBASE table,
the index contains only records that are unique with respect to the specified
index expression. For example, a .dbf file may contain "n" records, while the
unique index may contain "m" entries, where "n" does not equal "m." This means
that when the database is viewed by a UNIQUE index, it may appear to have fewer
records then it actually does. CAUSE There is no concept of primary indexes in dBASE prior to
version 7. Up to version 6, all indexes are taken as secondary indexes. The
dBASE command SET UNIQUE ON limits only which records are displayed. Access, however,
presently does not support dBASE later than version 6. RESOLUTION You can resolve this issue by one of the following three
methods:
REFERENCESFor
more information about linking to dBASE files, click Microsoft Access Help on the Help menu, type link dbase files in the Office Assistant or the Answer Wizard, and then click Search to view the topic. For additional
information about linking to dBASE files, please click the article number below
to view the article in the Microsoft Knowledge Base: 230125 ACC2000: Using dBASE Data with Access 2000 and Jet
The
third-party products that are discussed in this article are manufactured by
companies that are independent of Microsoft. Microsoft makes no warranty,
implied or otherwise, regarding the performance or reliability of these
products.
Modification Type: | Major | Last Reviewed: | 2/24/2003 |
---|
Keywords: | kb3rdparty kbprb KB199136 |
---|
|