If OR - Syntax?

[PaulSR]

Hello again,

Another problem I've looked around for but can't seem to solve - I'm trying to write a very simple if OR command but I keep getting a syntax error. I was looking at the reply from Marcus in this thread but it doesn't work for me.

post33869.html?sid=22da4c4b9936824946baa12192c62e72

Here's a stripped down slice - the problem is with the IF line obviously

Code: Select all

Let>FlagA=Y
Let>FlagB=Y

If>{(%FlagA="Y") OR (%FlagB%="N")}
    MessageModal>Yep
Else
    MessageModal>Nope
EndIf

Any help greatly appreciated !

Thanks,

Paul.

[Marcus Tettmar]

You have a missing '%' character. Should be:

If>{(%FlagA%="Y") OR (%FlagB%="N")}

Once the % is added it works correctly.

[PaulSR]

Oh dear how embarassing.

Thanks for that !

[PaulSR]

Tip for anybody else as what confused me (apart from the obvious missing %) was the fact that MS will report a syntax error if the variables haven't been set beforehand.

i.e if you take away one of the let> commands in the above code it'll report a syntax error followed by a parsing one which is slightly misleading (to me).

[Marcus Tettmar]

This is true for complex expressions (stuff inside {..}) because variables have to be denoted by %..% in complex expressions. So if the variable hasn't been set %var% resolves to just the string %var% but complex expressions also need quotes ".." and they aren't there, so it's a parsing error. If the variable exists and is found then the quotes are added. I suppose we could make it add quotes so that it is looking at literals but then you may not get an error/warning at all and may think it is working.

Outside of complex expressions where quotes are not needed you would not get an error because %var% is still a valid string.

We'll see if we can make the errors clearer

[jpuziano]

Thanks PaulSR for the TIP above and thanks Marcus for explaining what is going on... to see this in action, I just ran the following code:

Code: Select all

//Let>FlagA=Y
Let>FlagB=Y

If>{(%FlagA%="Y") OR (%FlagB%="N")}
    MessageModal>Yep
Else
    MessageModal>Nope
EndIf

---------------------------
Macro Scheduler
---------------------------
Line: 4 Syntax error
---------------------------
OK
---------------------------

---------------------------
Macro Scheduler
---------------------------
Line: 4 Error Parsing Expression
---------------------------
OK
---------------------------

Yes it would be great if one of these error messages could say something clearer, perhaps something like...

---------------------------
Macro Scheduler
---------------------------
Line: 4 Error Parsing Expression, Undefined Variable: FlagA
---------------------------
OK
---------------------------

Thanks!

[Marcus Tettmar]

As I said:

We'll see if we can make the errors clearer