Re: Testing for no input with CONSTRUCT stateme

The question has been raised regarding the test_select_all() function I posted last week why I simply didn't test like this: IF where_part MATCHES "*1=1*" THEN ... The answer is that I had thought that if I had a smallint field "num_1" and I was testing for a value of 1 (or 10, or 100, etc.) then I might come up with a statement that contained the string "1=1" that was a legitimate search. If some folks know for a fact that the CONSTRUCT statement will *never* build such a string except when escape has been hit on an empty screen, I'll use the test above, but I just couldn't be sure, and didn't have time to perform enough testing to ensure that it would *never* happen except in the one situation I was trying to test for. --- =============================================================================== Joe Hartley | jh@cadre.com - Whenever you find that you are on the Cadre Technologies | side of the majority, it is time to reform. - M. Twain 222 Richmond St. | -------------------------------------------------------- Providence, RI 02903 | Overman 1st Class - the Kilgore Trout Memorial Clench (401) 351-5950 x266 | of the Church of the SubGenius ===============================================================================