Set a value of a combo box to be results of a query

[shaunacol]

I have a table called tbl_Session which, when user logs on, records their Staffname, Stafflocation and current date time, it is not related to any other table. I then have a form called Frm_Order based on tbl_Order where the user can enter a new order. What would be extremely useful is if I could grab the fields StaffName and StaffLocation from tbl_Session and insert automatically into tbl_Order StaffName and StaffLocation for that particular order. I have tried setting the default value to a query based on tbl_Session where LogOffDate is empty (i.e current session). I have also tried writing some VBA for a Dlookup but I cant get the syntax right. Can anyone help please?

[ranman256]

When user clicks the CREATE NEW button,
open the form,
then set each field from the user info on the other form. This would happen on the FORM_LOAD event.
txtUser = forms!frmUser!txtStaffName
txtSession = forms!frmUser!ID

[shaunacol]

I'm sorry I think I may be confused. My user logon form will no longer be open as once they have logged on it automatically closes so I cant set my fields in the order form to be the same as my logon form fields (or maybe im misinterpreting?). I have to somehow get the data from tbl_session but since I need the current session then that's why I created a query that only has records where the LogOffDate is null (to capture current session). I hope that makes sense.

[June7]

Options:

1. save the info to global variables or TempVars

2. pass values to the OrderForm from the logon form and set unbound textboxes - I do this with form OpenArgs argument of DoCmd.OpenForm method

3. have a form that never closes (like a MainMenu) and pass values to that form so they remain available for reference anywhere at any time - this is what I do

4. DLookup() - post your attempted code
However, since this is a multi-user database, there could be multiple users logged on at the same time and therefore multiple records where LogOffDate Is Null - so I don't see this as a practical approach.

My db logon procedure pulls username from network and searches for that in Users table. If not found, they are a new user and they will be presented with logon form so a new record can be created. They never see the logon form again. This does take it for granted they are valid user because they logged into the network.

[shaunacol]

Many thanks for your reply, that makes sense, ill try that now