Re: Minor VFP Bug on Filter Expressions

Mmm. Just tried it - no difference. There doesn't seem to be any error checking.

Laurie

On 10 August 2016 at 06:08, Laurie Alvey trukker41@gmail.com wrote:

Not sure if this is relevant, but SET FILTER does not come into effect until the record pointer moves, Try this: SET FILTER TO <invalid expression> GO TOP BROWSE

Laurie

On 9 August 2016 at 21:20, Richard Kaye rkaye@invaluable.com wrote:

...

Interesting. It seems to be using the entire string from the first double quote to the second double quote as the filter expression and ignoring everything after that; almost like an inline comment. I did something similar on my system like this:

SET FILTER TO address1="529 and LEFT(country,2)="US"

SET([FILTER]) returns this:

ADDRESS1="529 and LEFT(country,2)="

Of course no records match that expression but it's not invalid.

--

rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Gene Wirchenko Sent: Tuesday, August 09, 2016 1:58 PM To: profoxtech@leafe.com Subject: Minor VFP Bug on Filter Expressions

Hello:

  I just ran into a minor bug in VFP on filter expressions.  I

typed the following: use cwko order tag cwkow set filter to clcode="KAK and left(wccode,2)="SP" browse and got an empty browse. What?

  I missed the closing quote after "KAK".  That second line

should have been: set filter to clcode="KAK" and left(wccode,2)="SP"

  I did *not* get an error on the original set filter line or the

browse despite the filter expression being invalid.

Sincerely,

Gene Wircheko

[excessive quoting removed by server]