I want to call a field from query that is self-contained in a report. How do I do this?
Beyond this, is there any performance difference between creating a query and having a self-contained query?
I want to call a field from query that is self-contained in a report. How do I do this?
Beyond this, is there any performance difference between creating a query and having a self-contained query?
A couple of questions:
1. Can you explain what you mean by 'call a field from a query'?
2. What do you mean by 'a self-contained query'?
Hi Robeen,
1. If I need to use a field I created in a query in a different form/report. How do I go about using it? Do I need to use an expression somehow, VBA functions, etc.?
2. Instead of creating a query that shows up on the side panel, I create a query within the report that never shows up on the side panel. I was actually unaware this was possible until a few days ago.
The query that you have within the report:
1. Where is the query typed in? Can you give me the exact text of the query?
2. Where does the data it retrieves show up? Is it in a field on the report?
If you want to use the same query in a different report - you can just copy the sql and link it to the field the way it is in the existing report - no?
1. The query is in the report. When you open the report and click the "..." for the Control Source, the query-builder appears. However, if you Close the query-builder before saving, it will ask if you want to Save. You have the option to save the query as a query that will appear on the control panel, or to be self-contained in the report only.
The created field in the query is:
Multiplication: [Field1]*[Field2]
2. The data appears on the Report. However, the field I created does not, as it is actually just a part of an expression for a textbox.
I don't want to use the same query in a different report, but I suppose I can create the same field and reuse it if necessary. I just thought there would be a way to call up a created field from a query.