[X]My Assistant

[ryan996]

Has anyone noticed any issues with the Expression Builder in the Access client?

I'm running Access 2016 Version 1803 Build 9126.2282.

The IIF expression is broken. Intellisense shows that the variables are separated with a pipe (|) when it used to be a (,) (ie. iif([column]>3,1,0)

All my old queries using a comma have changed to pipe but you can't actually build or save an expression with a | or a ,. Previous built queries will throw the error if you attempt to edit.

I'll probably have to escalate this to MS.

[Minty]

Does it do it on a brand new empty database? If not have you tried a compact and repair on the problem database.

If it does it on a new database, try an office repair.

[GroverParkGeorge]

No, this particular problem hasn't been widely reported that I know of.

Did Regional Settings on your OS get changed? Or options in your Access application?

Have you done a repair or reinstall of Office?

[GroverParkGeorge]

This was posted in the AWA forum, which I think is inappropriate for the problem, unless you are actually trying to work with an AWA? As you probably know, they are deprecated for Office 365. Of course, on-premises SharePoint supports them, so maybe that's where you are working?

[ryan996]

I am working on On-premises SharePoint.

George, thanks for reminding me that I recently changed regional settings on my OS to set | as a delimiter instead of (,). I was working in Excel and wanted to save a CSV as | delimited instead of (,). I'm certain this is what is causing the bug in the Access client.

[GroverParkGeorge]

I hope that works out.

How is it going with on-prem AWAs, btw?

[ryan996]

Yes, changing the delimiter settings in Windows back to (,) solved the issue.

On-Prem is working out fine. We had to upgrade from 12 to 16GB of RAM to get decent performance from the db.