Access Limitation

[Desmond]

Is there any way to increase the Access Index Limitation?

Number of indexes in a table 32; how to increase this value

 

[Rick B]

No, but why would you need to? If you are building a normalized relational
database, you should not have very many tables with more than 15 or twenty
fields anyway.

How many fields do you have and what type of data is being stored? Why
would you need to slow your database down by having it maintain more than 32
indexes?


Rick B


Is there any way to increase the Access Index Limitation?

Number of indexes in a table 32; how to increase this value

 

[Desmond]

Thanks, I am currently going through ODBC to access some
tables stored on a SQL server. I thought I would use
Access for the reporting feature that it has, so I was
linking to the table on the SQL server when Access
indicated that the table I am tryint to link has too many
indexes and I should delete some.

 

[Brian Camire]

You might try one of the following:

1. Create a view in SQL Server of the table and then in Access link to the
view instead of the table. Note that, by default, the linked view will not
be updatable. If you need it to be updatable, you need to define a "pseudo
index" *in Access* to identify which the field(s) whose values uniquely
identify each record. See the "CREATE INDEX Statement" help topic in Access
for more information.

2. If you cannot (or don't want to) create a view in SQL Server, but you
can live with the table being not updatable, you might try creating a
pass-through query in Access
instead of linking to your table (or view). Pass-through queries are not
updatable. See the "Send commands to an SQL database using a pass-through
query" help topic in Access for more information.

Hope this helps.

 

[John Vinson]

I was
linking to the table on the SQL server when Access
indicated that the table I am tryint to link has too many
indexes and I should delete some.

I had this error come up when trying to use ODBC to connect to a MySQL
database once; it turned out to be a problem with the ODBC driver
itself.

John W. Vinson[MVP]
(no longer chatting for now)