If a function such as Left is causing this issue, maybe it's because InvoiceNumber seems to be an incomplete reference:
((Left([InvoiceNumber],3))="LRG")
You have at least 2 tables involved in this query, but you don't seem to be telling Access which table that field comes from. I can imagine that would cause a not so clear message about not being able to use a function. So why would it work on some pc's? My theory is that different builds and/or Access versions seem to be at the root of other forum issues where the same thing that worked for ages no longer works. When you see the code or sql involved, it often is a wee bit sloppy in terms of references and the like. It's almost as if build updates become more particular about syntax. This would be the first time I've seen only one pc out of a group all running runtime to have such an issue, but I'd start by qualifying which table that field comes from. Actually, you seem to have a couple of other fields with the same sort of referencing.
Just a thought.
Last edited by Micron; 07-07-2020 at 08:54 AM.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.