To: Constant Reader who wrote (249 ) 12/8/2001 1:01:20 PM From: (Bob) Zumbrunnen Read Replies (1) | Respond to of 1003 Actually, that quirk has been with us since the pre-GNET days. I remember talking to Brad about it and his saying it was on his list of things to do, but comparatively low on the list. He had a lot of fires to put out while keeping a lot of plates spinning in the air. Basically, all searches were done through a roll-your-own indexing scheme since not only did SQL Server not have the built in ability to make indexes for text fields (to get away from the terribly slow LIKE search), but even now that it has it, a roll-your-own is generally the best way to go, IMO. A separate process (the "index bot") would parse a post 15 minutes after it was written and add words from it to the search index and those words were the searchable ones. The index for a particular message wouldn't (doesn't?) get removed if the message is deleted, though, and any post-15-minute changes aren't reflected either. Same with profiles and threads headers. The index entry is made at the time of creation, but isn't updated when a change is made. Interesting, though. I just did a search on "Zumbrunnen" and it didn't yield any results. But I remembered that I was often changing my last name to things like "Zumbrunnenowskianowiczatelli" as an inside joke between me and a friend (You still out there, V?). Of course, I couldn't remember any of those spellings. But I did remember that when "Pugs" was bashing me mercilessly on RB (as he's always done), and kept mispelling my name, I changed my name to match his spelling: "Zunbrunnen". I tried that, and it found me. Odd. That was not my original name and I probably changed it to that sometime last year. My guess is that the indexing got done when the database was switched, and the new system doesn't update the index on changes; just like the old system.