|
|
|||||||
Good Day all. The Search function seems to be FUBAR. I am searching on "ERRORS Error (317 / 13D) while retrieving error information for FFFFFFFD" and I get "We cannot proceed. All of your search keywords were too short. Please try again. Please use your back button to return to the previous page. " |
||||||||
|
|
|||||||
Works fine for me. Care to share what *exactly* you were entering int he various fields? |
||||||||
|
|
|||||||
It's the / in the search terms. If I copy & paste "ERRORS Error (317 / 13D) while retrieving error information for FFFFFFFD" (with the quotation marks) into the quick search field over on the right (or into the "Keyword Search Terms" field on the Advanced search page), I get that same message. Take the slash out, and I get a link to this very thread. |
||||||||
|
|
|||||||
hmm... the board should skip the quotes. at least it used to. just like google does if you have special chars inside your quotes. |
||||||||
|
|
|||||||
Same behavior without the quotes, btw. |
||||||||
|
|
|||||||
Further research showas that this error will be generated when an error trap is immediately after a loop statement.
|
||||||||
|
|
|||||||
comspec pause? why not "get $"? does the open() success? and at least one readline? |
||||||||
|
|
|||||||
comspec pause? why not "get $"? Because my golf handicap is huge does the open() success? and at least one readline? Yes the file opens successfully. This was just a dirty little script to test my theory. |
||||||||
|
|
|||||||
Boy, this thread went off in an unexpected direction! |