Conditional Build Expression

[Scott Prentice]

That *would* be sensible, but FM doesn't seem to allow parens in these 
expressions. It turns out that the NOT, when used within an expression, 
must be followed by AND .. and they must not be separated by a space. As 
in ..

	"Condition A" OR "Condition B" OR "Condition C" OR "Condition D" ANDNOT "Condition E"

Nice, eh?

...soctt



Lester C. Smalley wrote:
> Personally I would include parentheses to clearly indicate what the NOT
> clause applies to.  For example,
>
> ( "Condition A" OR "Condition B" OR "Condition C" OR "Condition D" ) NOT
> "Condition E"
>
> is quite different than
>  
> "Condition A" OR "Condition B" OR "Condition C" OR ( "Condition D" NOT
> "Condition E" )
>
> I suspect that Frame is generating the message because of the ambiguity
> of what NOT applies to.
>
> On  Monday, October 01, 2007 07:20 PM, Flato, Gillian wrote:
>  
> | I am trying to create a build expression but Frame keeps telling me
> that
> | I am building an invalid build expression. What is invalid about the
> | following expression:
> |  
> | "Condition A" OR "Condition B" OR "Condition  C" OR "Condition D" NOT
> | "Condition E"
> |  
> | Thank you,
> |  
> | 
> | Gillian Flato
> | Technical Writer (Software)
> | nanometrics
> | 1550 Buckeye Dr. 
> | Milpitas, CA. 95035
> | (408.545.6316
> | 7  408.232.5911
> | * gflato at nanometrics.com
>
>
> - Lester 
> -------------------------------------------------------
> Lester C. Smalley              Email: lsmalley AT infocon DOT com 	
> Information Consultants, Inc.  Phone: 302-239-2942 FAX: 302-239-1712	
> Yorklyn, DE  19736               Web: www.infocon.com	
> -------------------------------------------------------
>
>
>
>