Automatically Update Query Parameter w/ Code

[benthamq]

Hello,



I am totally new to Access 2010 and inexperienced.
I am trying to write code for an After Update event on a combo box (called Combo21 in my application) that will automatically supply a parameter to a parameter query based on the selection that the user makes in the combo box. The name of the query is qryUserPssPull and the parameter is enteruser.

I have written this for the After Update event:

Option Compare Database

Private Sub Combo21_AfterUpdate()
Dim userSelection As String
userSelection = Combo21.Text
DoCmd.SetParameter "enteruser", userSelection
DoCmd.OpenQuery "qryUserPssPull"
End Sub

But when I try to run it the error message I get is this:
Run-time Error '2766':
The Object doesn't contain the Automation Object, "Thomas."

(The combo box options are a list of employee names of which Thomas xxxxx is one. If I select a different employee name from the drop down list, I get the same message except with his/her name appearing in the error message.)

I apologize for the fact that this code probably demonstrates I am not too good at this...I am very much still learning.
I hugely appreciate any assistance offered. THANKS.

[June7]

Text is not the correct property, just drop it. The default property for data controls in VB/VBA is Value (VB.net uses Text), Value is the one you want.

I never open tables or queries. I open forms and reports bound to the tables or queries. So have never used the SetParameter method. Not having luck making it work.

Is this a multi-column combobox? Show the RowSource statement for the combobox. What is the structure of table the RowSource is based on? Is there an EmployeeID field? Really should search for the EmployeeID. Usually not good idea to search on names, what if you have several Thomas?

[benthamq]

Thank you for your help, the row source statement is this:

SELECT tblUsers.UserID FROM tblUsers;

The table has three fields, ID (primary key), Username, and Password.


Even so, again I appreciate your help and I am just going to mark this thread solved - I guess there is a way to achieve this but I understand entirely the logic behind only opening reports and forms bound to the tables and queries as you state and I think that is clearly a better method to pursue.

Thanks.