This is a discussion on GUIDs - Inetserver ; I am having trouble, still, with Indexing Services on Windows 2003 Server. What I have noticed in the Properties in Indexing Services, is that there are duplicates, but only for my custom metadata fields defined in the DefaultColumnFile registry entry ...
I am having trouble, still, with Indexing Services on Windows 2003 Server.
What I have noticed in the Properties in Indexing Services, is that there
are duplicates, but only for my custom metadata fields defined in the
DefaultColumnFile registry entry - the standard metadata GUID is
d1b5d3f0-c0b3-9a92-00a0c908dbf1 and I have this and
d5cdd505-2e9c-101b-9397-08002b2cf9ae. This only occurs for a few of my
custom fields - source, publisher and department. Strangely, with my custom
field decription, it has the GUID for metadata, but the field name
description0 (thats a zero on the end) it has the other GUID.
Now, being the cautious programmer I am, when I started using the
DefaultColumnFile pointer on my Windows 2000 Server, I commented out the
explicit oQuery.DefineColumn statements in my code. Upon un-commenting
these, I can now use these custom fields - it will only work with both the
DefaultColumnFile pointer AND the DefineColumn statement - whats happening
here?
I am also having trouble with the Write field date - but thats in another
posting.
Thanks
Stuart Doughty
doughtysm*@hotmail.com