To Access support/development team - NO INDEX clause in SQL Constraint still creates an index? Is it

  • Thread starter Thread starter Özden Irmak
  • Start date Start date
Ö

Özden Irmak

Hello,

In the Jet Sql 4.0 help file, it's mentioned that when you use NO INDEX
clause in a sql command which is going to cretae a foreign key relationship,
it shouldn't create any index for that column. But it doesn't seem to work.

My SQL command is like that :

ALTER TABLE [Tabel2] ADD CONSTRAINT [Tabel1Tabel2] FOREIGN KEY NO INDEX
([Veld1]) REFERENCES [Tabel1] ([Veld1]);

This clause creates an index with the same name as [Tabel1Tabel2] where it
shouldn't. Although when you check trough the Access index view it doesn't
show any index, when you check the table indexes with ADOX.Indexes there
you'll see that it has created an index with the same name.

Is this a bug or am I doing anything wrong?

Thanks in advance for your attention...

Özden
 
Özden: The consensus among the MVPs seems to be that it's an error in the
documentation. We haven't been able to get confirmation from Microsoft yet,
though.
 
Hello Douglas,

Thanks for your attention on this...

This is an important point for me as in a way I have to know that if I'm
doing something wrong or not so I can make the proper fixes/changes in my
tool to support/unsupport this kind of relations.

Thanks,

Özden Irmak
Klik! Software

Douglas J. Steele said:
Özden: The consensus among the MVPs seems to be that it's an error in the
documentation. We haven't been able to get confirmation from Microsoft yet,
though.

--
Doug Steele, Microsoft Access MVP

(No private e-mails, please)



Özden Irmak said:
Hello,

In the Jet Sql 4.0 help file, it's mentioned that when you use NO INDEX
clause in a sql command which is going to cretae a foreign key relationship,
it shouldn't create any index for that column. But it doesn't seem to work.

My SQL command is like that :

ALTER TABLE [Tabel2] ADD CONSTRAINT [Tabel1Tabel2] FOREIGN KEY NO INDEX
([Veld1]) REFERENCES [Tabel1] ([Veld1]);

This clause creates an index with the same name as [Tabel1Tabel2] where it
shouldn't. Although when you check trough the Access index view it doesn't
show any index, when you check the table indexes with ADOX.Indexes there
you'll see that it has created an index with the same name.

Is this a bug or am I doing anything wrong?

Thanks in advance for your attention...

Özden
Click to expand...
Click to expand...
 
Back
Top