Linking to Sybase Tables - Too many indexes issue

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

when trying to relink a table from Sybase warehouse to MS Access, I got the
message

"The operation failed. There are too many indexes on table <name>. Delete
some of the indexes on the table and try the operation again."

Having a snoop in the MS support site the official blurb was

""A table in a Microsoft Access database engine database can have no more
than 32 indexes. You cannot create additional indexes on a table with this
many indexes.
Delete one or more indexes from the named table and try the operation again"

We don't have rights to alter the Sybase tables. Is there any possible way
we can get MS Access to ignore this constraint? We can only alter the
properties of our Access instance.

BTW the Table we are linking to only has < 20 fields of which < 10 are
numbered the rest being text or dates. There are approx. 100K rows in the
table.

It's not the fact that the index is rolling over from 99999 to 100000?

Any assistance greatly appreciated.

Cheers,

Nedzer :)










(Error 3626)



"
 
There is no possible way to get Access to ignore this constraint.

Sometimes you can get ODBC drivers that do not report all
the indexes Can you get a driver that does not report FP indexes?

Can you add a view to the Sybase warehouse so that no
indexes are reported?

Can you add a new database to the warehouse so that you
can link through it to the data?

I think Access uses none of the indexes except one unique index,
and that only if you need to update the table.

(david)
 
Nedzer

Try replacing the linked table with a pass-through query (see documentation
in MS Access). That will hide the underlying table structure, but will allow
you to use the query in the same way as the original linked table was used.
Copy the connection string from the current linked table before you delete it
and then use it in the pass-through definition. If you use the same name as
the original linked table for the new query then your
forms/reports/quireies/code will continue to work as normal.
 
Back
Top