UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
 
   Reply to this topicStart new topic
> Access Client Expression Builder Is Broken, Access 2013 Web App    
 
   
ryan996
post Oct 11 2018, 05:28 AM
Post#1



Posts: 93
Joined: 16-June 13



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.

Go to the top of the page
 
Minty
post Oct 11 2018, 05:54 AM
Post#2



Posts: 90
Joined: 5-July 16



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.
Go to the top of the page
 
GroverParkGeorge
post Oct 11 2018, 06:44 AM
Post#3


UA Admin
Posts: 33,778
Joined: 20-June 02
From: Newcastle, WA


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?


--------------------
My Real Name Is George. Grover Park Consulting is where I do business.
How to Ask a Good Question
Beginning SQL Server
Visit My Blog on Facebook
Go to the top of the page
 
GroverParkGeorge
post Oct 11 2018, 06:48 AM
Post#4


UA Admin
Posts: 33,778
Joined: 20-June 02
From: Newcastle, WA


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?

--------------------
My Real Name Is George. Grover Park Consulting is where I do business.
How to Ask a Good Question
Beginning SQL Server
Visit My Blog on Facebook
Go to the top of the page
 
ryan996
post Oct 11 2018, 09:59 PM
Post#5



Posts: 93
Joined: 16-June 13



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.
Go to the top of the page
 
GroverParkGeorge
post Oct 12 2018, 08:23 AM
Post#6


UA Admin
Posts: 33,778
Joined: 20-June 02
From: Newcastle, WA


I hope that works out.

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

--------------------
My Real Name Is George. Grover Park Consulting is where I do business.
How to Ask a Good Question
Beginning SQL Server
Visit My Blog on Facebook
Go to the top of the page
 
ryan996
post Today, 02:28 AM
Post#7



Posts: 93
Joined: 16-June 13



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.

Go to the top of the page
 


Custom Search
RSSSearch   Top   Lo-Fi    19th October 2018 - 09:38 PM