"Order By..." code causes record mismatch?

[UserX]

I am very near completion of my new database, thanks to very insightful knowledge of June7 and Pbaldy, of course. My goal is to be able to select multiple records and append those selected records at the same time. Pbaldy gave me the idea (and code) to bring about a multiselect listbox. My listbox can either have the TimeHelped field editable by double clicking the record, and then typing the time value into the TimeHelped textbox below the listbox, which is what I want. The problem is that the listbox always sorts the record list alphabetically by customer's last name. My feeble attempt to fix this problem was to specify "Record Source = SELECT * FROM tblSign_in Order By Time_In DESC". Though this did sort the records from highest to lowest, the TimeHelped field, when updated, does not match the record selected. For example, in a list of five records, sorted by Time_In, from highest to lowest, the following results happened:

5. Updates record 1
4. Updates record 2
3. Updates record 3
2. Updates record 4


1. Creates new record entry with just the TimeHelped value

If someone would help me make sense of this, or suggest an alternative method of accomplishing my sorting, I would be eternally grateful. Attached is a sample of my db.

[June7]

Which form is involved in the issue?

[UserX]

forgive me. open nav pane, and open frmSI

[June7]

Suggest using the unique ID field in tblSign_in to identify the record to update then run an UPDATE sql instead of trying to find and edit a record in recordset. Why hide fields in the table?

Include the ID field as column in listbox. Then:

CurrentDb.Execute "UPDATE tblSign_in SET TimeHelped=#" & Me.Txt69 & "# WHERE ID=" & Me.Lst60.Column(x)

Then requery the listbox.

The TimeHelped input does not indicate AM/PM. Possibly Access will default to AM. Unless the input is 24-hour clock structure - is that what you intend?

[UserX]

June7, you're awesome! That works perfectly. Thank you so much!

I don't really remember why I hid the fields on the table. Using the 24-hour clock style is what we do here, so this works perfectly. Thank you again.