Re: If/Then in Access 2007

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Simple twist I learnt from C/C++, starting with the constant you want to check rather than the variable you want to check, but any 'side' is ok. In C/C++, = only means assignment, it is == which is used for comparison, so:

0 = variable

is catch by the compiler to be an error (you cannot assign a constant) while what you want is probably a test: 0 == variable. Doing

variable = 0

won't catch the error, and will place a zero in your variable. Bug hard to catch. So the 'twist' is to educate your mind to start with the constant. That possible bug does not exist in C#, since

if( variable = 0 )

is an error (can't cast an integer, 0, to a Boolean). The bug does not exists in VBA since = means and an assignment, and a comparison test and the compiler catches which one is which from the context.


Vanderghast, Access MVP


"Dale Fye" <dale.fye@xxxxxxxxxx> wrote in message news:904350AD-2CD4-447E-A7D4-A0EF0994B960@xxxxxxxxxxxxxxxx
Michel

Any particular reason why you used the syntax:

0 <> len(office111 & "")

instead of:

len(office111 & "") <> 0

I've always put the expression to be evaluated on the left of the comparison
operator(s) , and was just wondering whether there is a reason for doing it
in reverse?

----
Dale



"vanderghast" wrote:

IIf([Office111]<>"" , "+" , "" )
& [Office1] & " " & [Office11] & " " & [Office111]


Note that when you say "empty" , I assume you mean just that, a string with
no character in it. IT IS NOT the same as being NULL (unkown data, not
available, not appropriate, ... ). If you have to include also this case,
try:

iif( 0 <> len(office111 & "") , "+", "" )
& ...



Vanderghast, Access MVP



"Thomas Hirschmann" wrote in message
news:20091027104457tmh@xxxxxxxxxxxxxxxxxxxx
>I can't figure out the "IF" code for the follwong list I'm trying to
>compile:
>
> The "Table" field I'm trying to query is "Office111". If that field is > not
> empty, a "+" should be added to the output document. If the "Office111"
> field is empty, then nothing should be added. I tried this but I'm > getting
> "The expression you entered contains invalid syntax".
>
> CHNummer: IIf([Office111]<>"" "+") & "" & [Office1] & " " & [Office11] > & "
> " & [Office111]
>
> Any help would be most appreciate. Thanks.
> Tom
>
>
> EggHeadCafe - Software Developer Portal of Choice
> Full-Text Search with SQL Server 2000
> http://www.eggheadcafe.com/tutorials/aspnet/7e941095-d74f-449d-8f52-e6f5b6320397/fulltext-search-with-sql.aspx

.


.

Relevant Pages

  • Re: Compiler quality (was: Extending discriminant types)
    ... files they use for syntax checking for each Ada specifications. ... even are clarified as BUG free. ... error is not a compiler BUG. ...
    (comp.lang.ada)
  • Re: Tcl Switch case
    ... My thesis is that there could be a good reason to change the syntax of ... a command, and one reason is to align with what the byte compiler ... bug has persisted for 15 years, but has never kept anyone from writing ...
    (comp.lang.tcl)
  • Re: If/Then in Access 2007
    ... Bug hard to ... the compiler catches which one is which from the context. ... Note that when you say "empty", I assume you mean just that, a string ... "The expression you entered contains invalid syntax". ...
    (microsoft.public.access.queries)
  • Re: C90: empty statement mixed with declarations?
    ... statements (even empty ones) cannot be mixed with declarations. ... tried to compile it with a more finicky compiler. ... unit that contains a violation of any syntax rule or constraint. ... What is missed here is to show if 'declaration' can produce a lone ...
    (comp.std.c)
  • Re: Simple output problem
    ... it can be a difficult bug to find because the compiler ... isn't going to complain because it is valid C syntax. ... Prev by Date: ...
    (comp.lang.c)