two possible reasons. This looks like an example of a common trap where unwittingly you have included IntervalMonth as part of a literal string and not a variable to be passed to an expression (or sometimes a function). Think of it this way. The sql statement starts and ends with double quotes. Everything in between that is recognized as an object such as a table or field, or an Access 'command' such as INNER JOIN can be evaluated. A custom function or variable cannot - so you have to concatenate.
(removed example as it reflects the post that just beat me to it)
However, if the suggestion solves one issue, I think this could cause the same issue: =[Forms]![CreateInvs]![LeaseTerm_ID]))
Tip: Please use code tags around anything more than a few lines and use customary indentation. Code is much easier to read that way.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.