Mike Yearwood
Toronto, Ontario, Canada
General information
Category:
Visual FoxPro Beta
and you'll find your performance goes down, because the evaluate will happen per row in the table.
>I may have figured this one out! VFP9.0 (beta) does not allow macro-substitution in a View definition using the (&) ampersand.
>
>Using paranthesis () for macro-substitution doesn't work either because the View Designer uses them to seperate values.
>
>I think I got around the problem by using the Evaluate() function.
>
>I will test it and also try to see if having this "function" in the where clause will cause a significant slow down.
>
>BROKEN CODE:
> select * from ji!wo where &vcWhere
>
>FIXED CODE:
> select * from ji!wo where evaluate(vcWhere)
>
>*Note - When using "&vcWhere" in previous version of VFP, you did NOT want vcWhere to be defined. When using the "evaluate(vcWhere)", vcWhere MUST be defined to avoid an error.
>
>Thanks,
>Paul
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only