Taking a cue from my own description, I deleted all the indices by toggling the setting. It seems to be back to fully functioning search again. There must have been something in those indices that caused some confusion for the system.

On 12/12/19, 10:57 AM, "Douglas Palmer" <[log in to unmask]> wrote:

    And yet, there have been changes in how it works. I am not saying there is a bug or anything, just that searching is not what it used to be. It may be a corrupt index somewhere or something else local to our system, but it is not behaving the same and the change was quickly noticed when we went to 17.0. This was the first time in I believe 20 years that I was ever asked what an "overflow word" was and how to fashion a search to avoid them (and I got dozens of people asking the same question immediately on installation of 17.0). With DBRINDEX turned on, almost every search returns nothing. Turning it off "fixes" the problem. The root cause may be somewhere else.
    
    -- DCP
    
    On 12/12/19, 3:18 AM, "LISTSERV Site Administrators' Forum on behalf of Eric Thomas" <[log in to unmask] on behalf of [log in to unmask]> wrote:
    
        There have been no code changes to searches or indexing in 17.0.
        
          Eric
        
    

############################

To unsubscribe from the LSTSRV-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1