Re: Testing for no input with CONSTRUCT statement

In article <duhonCKIA2w.EoK@netcom.com> duhon@netcom.com (Joey Duhon) writes: >> I had a situation where I wanted to prevent the users of a query screen from >> simply hitting the escape key and selecting every row in a table. My >> problem was that we are using the CONSTRUCT statement to generate the WHERE >with v4.0 and 4.1 the string is " 1=1". it seems unlikely that this will >change. use a character comparison on the whole string. matches can fail: > "*1=1*" matches "rate1=15.3" I have the same problem. Usually I am forced to get_fldbuf() each field and verify the CONSTRUCT. Usually I have at least ONE field that is 'required' and thus saves me a lot of heart ache. But this is something Informix does need to enhance/expand. -- Harry Skelton - 1848 Beaver Dam Lane - Marietta, Georgia - 30062 404-590-7100 or 800-366-8181 Work -- 404-578-8085 Home 404-590-0355 - Personal Fax My opinions are my own. Use at your own risk.