This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I am experiencing error 2482 when trying to run an Access macro that contains a step with an expression. Macro runs fine until that step. Database is in a trusted location, but CurrentProject.IsTrusted=False. Running Windows 11 on PC.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I think, with your help, I'm learning something new. I have not tried a data macro before, but it looks like exactly what I need. I will do some experimenting and get back to you later, if that is OK.
They're all tools in your arsenal. You just need to choose the correct one to use based on your goals.
">
I created a totaling query on the table (Total: Sum) and created another macro as
SetLocVar
Name: Test
Expression = {Query1]!{SumOfValue1]
Running the macro produces the same 2482 error message.
I should note that the database is in a trusted location, but when I examine CurrentProject.IsTrusted (with macro named "AutoExec"), result is False.
Right. The basic premise is that you can't basically "look into" the values inside a table from within a saved macro, you'll have to use a function to do that (or use a data macro). That is why I recommended using DSum(). Have you tried it yet? Are you not able to use it?
I think, with your help, I'm learning something new. I have not tried a data macro before, but it looks like exactly what I need. I will do some experimenting and get back to you later, if that is OK.
Perfect! I can't thank you enough for your help.
I think the problem here is that an aggregation operator like SUM in a query is qualified by the HAVING operator, not the WHERE operator, i.e. it operates on the aggregated value after grouping. If you want to, use the WHERE operator to operate on an aggregated value, a subquery would normally be used. The VBA aggregation operators like DSum operate in the same way as a subquery, so can be used in a macro in the same way that they can be used in a WHERE clause in a query.
