Share via

!missingoperator mergefield problem

Anonymous
2017-12-15T16:43:43+00:00

I have the following formula inside a formula

{= 0.1 * {= {Field} / 10}}

When I select {= {Field} / 10} and press Shift+F9 the result is correct.

When I select the {= 0.1 * {= {Field} / 10}} an press Shift+F9 it returns !missing operator.

Even more puzzling this only happens with one of the records of the mail merge, when I do the same using other record as an example it works just fine. and just in case is relevant the field value is 101 in the record that fails and is 011 and 111 in the records that work.

Why?? 

Any help is appreciated...

N

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Paul Edstein 82,861 Reputation points Volunteer Moderator
    2017-12-15T21:28:35+00:00

    Your thread title refers to a mergefield, but there is no evidence of one in the body of your post. For example, if there were a mergefield, I'd expect to see:

    {= 0.1 * {= {MERGEFIELD Field} / 10}}

    or:

    {= 0.1 * {= «Field» / 10}}

    That said, it seems you could get the same results with:

    {=0.01*{MERGEFIELD Field}}

    or:

    {=0.01*«Field»}

    As for the record whose field doesn't 'work' in the formula, you might check that the number is all the field contains.

    Note: The field brace pairs (i.e. '{ }') for the above examples are all created in the document itself, via Ctrl-F9 (Cmd-F9 on a Mac); you can't simply type them or copy & paste them from this message. Nor is it practical to add them via any of the standard Word dialogues. Likewise, the chevrons (i.e. '« »') are part of the actual mergefields - which you can insert from the 'Insert Merge Field' dropdown (i.e. you can't type or copy & paste them from this message, either).

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments