Similar Threads:
1.AND OR operator won't work
With a mail merge I want to check if the fields "company" and "name" are
filled (not empty)if this is true then the text "attn. " has to be placed
before the name. Somehow it won't work, does anybody know why?
{COMPARE{MERGEFIELD company} <>""}
{COMPARE{MERGEFIELD name}<>""}
IF{=AND({COMPARE{MERGEFIELD company} <>""},{COMPARE{MERGEFIELD
name}<>""})}=1 "true" "false"}
Here the result of some fields:
0
1
false
1
1
false
The first two comparisions went well, the AND function doesn't seem to work,
whatever I change it remains "false", even if I replace AND with OR. Please
help.
2.Contact Searching - idiot operator
Outlook 2007. I cannot for the life of me get search in contacts to turn up
a thing. Clearly I have some setting somewhere set to results=0 but I can't
find it.
I have 847 items in Contacts. I have 2 people named Alice. I can see both
entries on my main contacts screen. Yet, when I plug in the word Alice in to
'search all Contact Items', I get the All Contact Items (Search Results)
screen with a note that says 'No matches found for "alice". Same results if
I only plug in the letter 'a' - 'No matches found for "a".
This is driving me nuts.
I have the same set of contacts on a different machine running Outlook 2003.
If I plug 'alice' into that search, I get the two Alices. So, while I'm an
idiot, the condition apparently only started in 2007 :)
Where can I start to look for what's preventing the proper search results?
3.Ampersand operator in Header
I want to create an Excel yearly form with the only current year in the Header
Entering &d will give the current date but I only want the year. Entering
&[YEAR] or &y doesn't work. This form is to be used on a club computer in
which none of the members would be capable of creating a header by just going
to View>Headers and Footers and have the Header display 'Annual Sale 2005'
4.Differential (upright "d") in Eqn Edtr is OPERATOR not function
5.[CZT-Devel] help with token's for operator word's
Hi Mike,
XXXX@XXXXX.COM wrote:
|>No "\dom" is just a NAME too.
|
| The concrete parse tree of birthday book example in the standard maps
| \dom to PRE?
|
| What would happen if was declared it as a PRE and it did parse like the
| ISO example?
|
| Would it cause any problems with other declarations?
|
\dom could be declared as PRE, but I think allowing function
applications such as "Expression Expression" is good in Z,
otherwise every time one wanted to declare a prefix function, they
would have to declare an operator template for it, which would
have an impact on a lot of existing Z specifications.
| In Fig1 it looks like \dom is performing an action on birthday which is
| how it should work.
|
| The parsing would work like this:
|
| (Going form bottom up)
|
| 1) pass birthday into \dom
| 2) \dom will check if it's declaration can accept birthday's parameters
| see Fig1
| \dom can accept a set that is a mapping of 2 parameters, see Fig3
| (\dom : (X \rel Y))
| 3) Check to see if the passed set is also a mapping of 2 parameters,
| Fig2
| (birthday: NAME \pfun DATE)
| 4) Yes it is
| 5) Then make sure that what we return will also be a mapping, a
| functional mapping of all the X, (\fun \power X)
| That holds true for:
| \forall r : X \rel Y @ \dom r = \{~ p : r @ p.1 ~\}
|
I'm not sure I follow this. Steps 2-5 seem like type inference to
me, not parsing?
| Now going back to Fig1, Application contains a set who's constraints
| meat a condition that is working on a set called birthday, because
| application is the right side of the infix relational predicate "=" and
| the left side is DeclName (know) then point know to the set returned by
| Application.
|
| If I call \dom NAME and birthday NAME I can't do the above?
|
Hmm... I don't understand. Are you saying that you that the
production "Expression = Expression Expression" (from the concrete
syntax in section 8.2) cannot be parsed by a recursive decent parser?
Cheers,
Tim
6. help with token for operator words
7. "Only ignored words" with AND operator
8. operator word's fields object with vc++