Re: 4GL CONSTRUCT...

Be careful when searching for the quotes, though. I've discovered that different versions of 4GL generate different quotes. The older versions seem to use double-quotes while newer versions (4.14+) use single-quotes. That was a gotcha that just bit us when testing the Y2K complient versions. We added the test "if construct_txt matches "*'*" then ... else if construct_txt matches '*"*' then ... then we do further checking using the appropriate quotes. Nils Myklebust wrote: [snip] > > I assume this is what the user typed into the field: > <>Martin* > and this is what the construct statement itself created: > name <> "Martin*" > Of course this is "wrong". However it is easy enough to scan through > the char variable looking for <> followed by a set of quotes. > Then look inside the quotes and see if you find a ? or * (and possibly > [ ] if you want to support those). If you do replace the <> with > matches and you are done. > > There may be cases where this doesn't work, but I doubt it. Just test > a little and see. -- ____________________________________________________________________ | Colin McGrath cmm@trac3000.ueci.com | Raytheon Engineers & Constructors, Inc. (215) 422-4144 | Philadelphia, PA, USA | Any opinions I state are my own and not necessarily of my employer |___________________________________________________________________