No Index on linked tables

[Rover]

When I create an index on a table, and then link it from another
database, the link doesn't show the index. Am I missing something here?
Shouldn't the fields be indexed as I defined them even though they are
linked?

 

[Brendan Reynolds]

I haven't been able to reproduce this. In my tests (Access 2003) indexes I
added to a table were immediately visible in the link.

We are talking about a linked Access table, not some other type of database?

 

[John Vinson]

When I create an index on a table, and then link it from another
database, the link doesn't show the index. Am I missing something here?
Shouldn't the fields be indexed as I defined them even though they are
linked?

If the index exists in the backend where the table itself resides, it
will be used by Access. How are you expecting it to "show" the index?

John W. Vinson[MVP]

 

[Rover]

In the backend database (A2K) I can go into design view and see the
indexes. When I am in the frontend (A2K) and look at the linked table
in design view, I can see the keys but in the index field it has "no"
for all of them.

 

[Rover]

I've found out the tables I'm looking at are really Cobol files using a
product called Relativity to make them ODBC compliant. They are then
linked in to Access. But the problem I have is the same... I can see
the key but not the indexes. If I look at the same tables use another
product called WinSQL, I see the indexes.

Any ideas?

 

[Rover]

Brendon,
Will Access pick up links from other dataBases, generally speaking?

 

[Brendan Reynolds]

You can link to or import data from (versions of) dBase, Excel, Exchange,
HTML, Outlook, Paradox, text files, Windows Sharepoint Services, and any
database for which an ODBC driver is available, including (but not limited
to) FoxPro, Oracle, and SQL Server.