Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 135384 - Last Review: December 3, 2003 - Revision: 3.1
FIX: Unbalanced Parentheses in IF Condition Not Seen by Parser
This article was previously published under Q135384
You receive incorrect results from an IF...ENDIF when you have unbalanced
parentheses in the logical expression or if the later part of the
expression has a syntactical error and the beginning of the expression can
be logically evaluated.
This is a compatibility issue. Anything that cannot be logically parsed
in the expression is treated as a comment on the same line if at least some
of the first part of the expression can be evaluated to a logical value.
Microsoft has confirmed this to be a problem in the Microsoft products
listed at the beginning of this article. This problem has been fixed in
Visual FoxPro 5.0 for Windows.
Code to Reproduce Problem
IF (.F.)) OR (.T.)
?"true"
ELSE
?"false"
ENDIF
APPLIES TO
- Microsoft Visual FoxPro 3.0 Standard Edition
- Microsoft Visual FoxPro 3.0b Standard Edition
- Microsoft FoxPro 2.6a Standard Edition
| kbbug kbfix kbvfp500fix KB135384 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please