BUG: "Alias Not Found" Occurs with Table Used in dBASE Query
Article ID: 114144
Article Last Modified on 10/16/2002
APPLIES TO
- Microsoft Visual FoxPro 3.0 Standard Edition
- Microsoft Visual FoxPro 5.0 Standard Edition
- Microsoft Visual FoxPro 5.0a
- Microsoft FoxPro 2.6 Standard Edition
- Microsoft FoxPro 2.6 for MS-DOS
This article was previously published under Q114144
SYMPTOMS
An "Alias Not Found" error message occurs when you are opening tables in
FoxPro that were used for queries in dBASE.
CAUSE
This problem may occur because the dBASE query indexed the table on a field
from another database, placing the key in a temporary index file. When the
table is converted, FoxPro duplicates the foreign key, but places the
foreign key in the permanent structural index for the current database.
When you attempt to open the database outside the query, an "Alias Not
Found" error will occur.
RESOLUTION
You must delete the offending index tag before you can access the file
without error.
STATUS
Microsoft has confirmed this to be a problem the Microsoft products listed
at the beginning of this article.
Additional query words: convert kbvfp300 kbvfp500 kbvfp500a
Keywords: kberrmsg kbbug kb3rdparty KB114144