M
mhenshaw76
Hi there-I have yet to find an answer for this issue. I have tables that are
in an SQL environment that I then link into an Access 2000 database. In SQL,
some indexes are created on the fields-some of the indexes are on multiple
fields. The indexes are not primary and not unique. For some of the tables,
when I create the linked table, I get the indexes coming in just fine. I
never select a unique record indicator when prompted since there are rarely
instances where any field is 'unique' in that way (any of them give me the
primary key if I were to click on them which would mess with how the data is
presented). The problem is that some of the tables, which I know have indexes
on them in SQL-do not have the indexes coming along with them when I link
them in Access 2000. Previous versions of the database, in Access 2000, have
not had this issue. The version of SQL is also the same. I am stumped as to
what can be causing this-is it a 'bug' in Access 2000 or in SQL? Any other
ideas would be welcome-thanks so much!
in an SQL environment that I then link into an Access 2000 database. In SQL,
some indexes are created on the fields-some of the indexes are on multiple
fields. The indexes are not primary and not unique. For some of the tables,
when I create the linked table, I get the indexes coming in just fine. I
never select a unique record indicator when prompted since there are rarely
instances where any field is 'unique' in that way (any of them give me the
primary key if I were to click on them which would mess with how the data is
presented). The problem is that some of the tables, which I know have indexes
on them in SQL-do not have the indexes coming along with them when I link
them in Access 2000. Previous versions of the database, in Access 2000, have
not had this issue. The version of SQL is also the same. I am stumped as to
what can be causing this-is it a 'bug' in Access 2000 or in SQL? Any other
ideas would be welcome-thanks so much!