A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

"Hexidecimal" Index



 
 
Thread Tools Display Modes
  #1  
Old December 14th, 2009, 01:19 AM posted to microsoft.public.access.tablesdbdesign
gmg
external usenet poster
 
Posts: 7
Default "Hexidecimal" Index

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
  #2  
Old December 14th, 2009, 03:17 AM posted to microsoft.public.access.tablesdbdesign
Allen Browne
external usenet poster
 
Posts: 11,706
Default "Hexidecimal" Index

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


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 10:32 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.