ACC: Index Missing for Attached FoxPro or dBASE Table (122561)
The information in this article applies to:
- Microsoft Access 2.0
- Microsoft Access for Windows 95 7.0
- Microsoft Access 97
This article was previously published under Q122561
Moderate: Requires basic macro, coding, and interoperability skills.
SYMPTOMS
When you open a linked (attached) dBASE or FoxPro table in Design view, the
table's index is missing, even though you specified an index when you
linked the table.
RESOLUTION
When you link a dBASE or FoxPro table, make sure that the index that you
specify is based on a single field or a simple concatenation of multiple
text fields. An index based on a more complex expression may not be visible
in Microsoft Access.
MORE INFORMATION
A dBASE or FoxPro index based on a complex expression (anything other than
a single field or a simple concatenation of text fields) may cause the
Microsoft Jet database engine used in Microsoft Access to form incorrect
joins because of incorrect assumptions about the order of the keys. For
example, an index based on "string1 + function(string2)" may appear to the
Microsoft Jet database engine to be based on "string1, string2." The
Microsoft Jet database engine will not use such indexes, and will not
display them in the Indexes window.
The indexed sequential access method (ISAM) driver used by Microsoft Access
will, however, attempt to maintain an associated dBASE or FoxPro index
while the ISAM is updating the dBASE or FoxPro table even though the index
is not visible in Microsoft Access.
dBASE is manufactured by Borland International, Inc., a vendor independent
of Microsoft; we make no warranty, implied or otherwise, regarding this
product's performance or reliability.
REFERENCES
For more information about linking FoxPro or dBASE files, type "FoxPro" in
the Office Assistant, click Search, and then click to view "Import or Link
FoxPro or dBASE files".
| Modification Type: | Major | Last Reviewed: | 5/6/2003 |
|---|
| Keywords: | kb3rdparty kbprb KB122561 |
|---|
|