I have a database that has been fully operational for over a decade. It ran without issue in 2007 but after changing to 2019 I'm getting a "There isn't enough memory to perform this operation..." error message.
I'm a heavy macro user and there were two errors in syntax in the old version...
I don't understand it. I went back and logged in about three hours later and it worked as it always had. I don't believe in miracles but I just experienced one.
Thanks for trying. If the problem returns I'll let you know but for now I'm able to work normally.
I am working remotely on a database. I've been able to open reports without issue and suddenly I'm getting the above message. I don't have access to printers and I can't even open the reports in design view. Can you provide some assistance please?
As always, all help is greatly appreciated.
I really appreciate all the help. Other forums allow you to give a star or some sort of extra credit or special thanks to people that helped you but I don’t see that option here. Is that option available? And if so, how do I find it? I would really like to thank everyone that helped me.
Yessssss! I played with the parameter values, but I was trying to use the field names in the query, and it failed.
when I selected the temporary variable name or the form field name then it worked just fine.
I believe the issue is resolved based on the parameters. Thank you all for all of your...
I’m confused. I now understand how to find the parameters so it’s not a problem for me to do. I’m just trying to understand what my objective is.
Just to reiterate, the field whose data I am trying to limit is from one of the Select Queries and not from the Crosstab.
In this instance do I...
Thank you very much. I would like to pass on the results of my testing.
I completely removed the Crosstab Query from the source Select Query and the problem went away. You were right. It’s related somehow to the Crosstab Query.
However, I did exactly as suggested. I right-clicked on Query...
I have another question. Why does the exact same text manually typed work and yet it fails with that error message as a variable?
Can you imagine any reason for that?
MajP and CJ, can you please explain what you mean by declaring the parameters? I'm not sure I understand.
Yes, the error message is as you mentioned, and as I said one of the source queries is a Crosstab, but the specific field that I'm applying the criteria to is not from that query, but from...
What threw me off is that this issue appeared the first time I attempted it in 2016 and so I assumed it was a version issue rather than something else.
I remember now that “assume” makes an ass out of u and me!
I’ll keep you posted now that I have a direction to follow.
I have more info. I tested the same TempVars in another query and it works normally so clearly something else is wrong.
I will test and let you know what I find.
Thank you all for your help.
I am in error about something. The query in question is a Select Query but one of the source queries is a Crosstab Query.
However the field I am attempting to add a criteria to comes from a source Select Query and not the Crosstab.
Access 2016 actually fills in the form parameters for you. I type Forms! And a drop-down list of form names appears. I select a form and another drop-down list if field names appears to select from.
Because of that I am confident that the name is entered correctly and that there is no typo.
Thank you all for your quick and thorough replies.
It is a Select Query that I’m working with. And I have just switched from 2007 to 2016, and this is the first effort so I have not tried other queries.
I can tell you that it works if I type the limiting text in directly instead of trying to...