When you create a relationship with referential integrity (RI) enforced,
Access creates a hidden index to manage the RI. It attempts to create an
index name such as Table1Table2. If that name is taken, it uses a GUID
(globally unique identifier.) Looks like what you struck.

You can't remove the relationship and leave the RI intact. You could remove
it, and then enforce the rule in SQL Server.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.


"gmg" wrote in message
...
I have used the Access Documenter to list the indexes in my tables.
Several of the tables have an Index that looks like it's in Hexidecimal.
Ex: C1D060E6-4206-11D7 etc.
I never created it and don't know what it's for.
When I migrate to SQL Server, there is a warning that it could cause a
conflict.
Does anyone know where this index could have come from?
If it isn't necessary, how can I remove it?
Thanks