Can you do a select command for a query?
- Thread starter cheberdy
- Start date
Select * from query
- Local time
- Today, 04:30
- Joined
- Oct 29, 2018
- Messages
- 22,624
Okay but where does the "command" come in?
Last edited:
- Local time
- Today, 07:30
- Joined
- Feb 19, 2002
- Messages
- 47,553
Queries and tables are interchangeable for many uses. That is why Access combines their name spaces. For example, you can have a report named Annual and a form named Annual and a table named Annual and Access doesn't care. But you cannot have both a table named Annual and a query named Annual because Access couldn't tell which you were referencing.
Just substitute the name of a querydef in place of a table name. The query must be a select query. It cannot be an action query when you want to use it in place of a table.
Just substitute the name of a querydef in place of a table name. The query must be a select query. It cannot be an action query when you want to use it in place of a table.
How hard would it have been finding out by trying yourself?
- Local time
- Today, 06:30
- Joined
- Feb 28, 2001
- Messages
- 30,474
If I understand your question, the strict technical answer is "NO" because a query is an example of set theory. The query ALWAYS selects ALL conforming records at once.
HOWEVER,...
Depending on how you interact with the record set that results from the query, a specific record selection can occur that is analogous to selecting a row in Excel or a sentence in Word. I suspect that this is what you mean by "select command."
In the query itself, a WHERE clause can restrict which records are returned in the record set. Depending on the table structure and any available discriminating fields, you can select everything, many things, one thing, or nothing.
In a true DAO or ADO recordset that opens a query, there is a current record that is selected and that selection can be changed by .Movexxx or .Findxxx methods applied to the recordset's controlling object (called a Recordset). Here, you interact with the control mechanism used to expose the records of your recordset and that allows you to "make a selection." This is always one-at-a-time.
On a datasheet display and on a continuous tabular form (both based on queries), you can select and highlight a specific record. Here, you are interacting with the graphic mechanism used to display the records. It is possible to select multiple records at once but interacting with them will be limited.
On a form based on a query, you can navigate to and display the contents of a record. Here, you are interacting with the form's built-in navigation methods that are based on a behind-the-scenes recordset. For standard forms, this is primarily one-at-a-time, but there are some advanced methods to change that.
If this comes closer to what you wanted, please specify the context in which you wanted to make your selection so we can properly guide you.
HOWEVER,...
Depending on how you interact with the record set that results from the query, a specific record selection can occur that is analogous to selecting a row in Excel or a sentence in Word. I suspect that this is what you mean by "select command."
In the query itself, a WHERE clause can restrict which records are returned in the record set. Depending on the table structure and any available discriminating fields, you can select everything, many things, one thing, or nothing.
In a true DAO or ADO recordset that opens a query, there is a current record that is selected and that selection can be changed by .Movexxx or .Findxxx methods applied to the recordset's controlling object (called a Recordset). Here, you interact with the control mechanism used to expose the records of your recordset and that allows you to "make a selection." This is always one-at-a-time.
On a datasheet display and on a continuous tabular form (both based on queries), you can select and highlight a specific record. Here, you are interacting with the graphic mechanism used to display the records. It is possible to select multiple records at once but interacting with them will be limited.
On a form based on a query, you can navigate to and display the contents of a record. Here, you are interacting with the form's built-in navigation methods that are based on a behind-the-scenes recordset. For standard forms, this is primarily one-at-a-time, but there are some advanced methods to change that.
If this comes closer to what you wanted, please specify the context in which you wanted to make your selection so we can properly guide you.
