MS Access: Unexpected 'Field Not Found' scenarios When Using Calculated Control in Report
I've been banging my head against this for hours. I've searched everywhere and can't find a clear answer. I've encountered a strange issue with I've encountered a strange issue with I've been struggling with this for a few days now and could really use some help. I'm working with a frustrating scenario in MS Access 2019 where I receive a 'Field Not Found' behavior when trying to run a report that includes a calculated control. The calculated control is based on a field from a query that includes a GROUP BY clause. Here’s the control source of the calculated field in the report: ```sql =Sum([OrderAmount]) ``` The query that the report is based on is as follows: ```sql SELECT CustomerID, Sum(OrderAmount) AS TotalOrders FROM Orders GROUP BY CustomerID; ``` When I preview the report, I get the behavior message stating that '[Field Name] Not Found'. I double-checked the field names in the query and confirmed that 'OrderAmount' is indeed present and correctly spelled in the original 'Orders' table. I even tried refreshing the report and compacting the database, but the behavior continues. Additionally, I verified that the control is properly referencing the calculated field in the query, but I still face this scenario. I've tried using the field name directly as well as its alias from the query, without success. Is there a special consideration or limitation I might be missing when using calculated controls in reports based on grouped queries? Any insights would be greatly appreciated! This is part of a larger web app I'm building. Is there a better approach? I'm using Sql 3.9 in this project. The project is a microservice built with Sql. Thanks, I really appreciate it! I'm on Ubuntu 20.04 using the latest version of Sql. Any pointers in the right direction? I'm using Sql 3.11 in this project. Am I approaching this the right way?