I use a password manager app on my phone. I suppose if someone murdered me and then opened my phone and app with my dead face, my passwords would be compromised.
“Name” is a horrible choice for the name of anything in Access since every table, field, control, object, … has a Name property. Use a name that isn’t a reserved word such as FirstName, LastName, or FullName.
I think the error is:
Me.selAlpha & "" = ""
What exactly are you attempting to do. There should only be the variable or a control name to the left of the =.
This is a very simple query once the specifics are made known.
Are you looking for a date range?
What are the potential value is the Fee Type field? Normally there would be a small table of Fee Types with a combo box to select the appropriate type. A simplified query with one amount of days...
Does each Group Member pay a fee or is the fee per group? If the start date is February 1st and the end date is February 2nd, is that one day or two? How does Fee Type affect the desired result?
You can't get "last" without using a date/time field. It would help if you provided some more complete data with the significant fields and some sample records.
Are you changing the subform in design mode as a child of the main form or are you opening the subform on its own to make the update? I prefer to open the subform on its own.
I don’t see any code that actually creates a recordset. I think you could use simple DSum() or DCount(). Warnings could be simple Conditional Formatting.
Add the data to the record source of your main report. Let's say your main report is the employee table and the subreports are based on Employee Hours and Employee Payroll. Create to totals queries of Employee Hours and Employee Payroll that group by employee. Add these two queries to your main...
I doubt I have an answer but do have questions. Are these action queries? Do they need to allow edits? Can they be pass-through queries?
Why are you opening queries? Is this part of your user interface?
I would attempt to move as much work as possible to the server.
If you already have the number you are looking for in another query, why not add that query to your report's record source? Join on the appropriate fields so you don't end up with more records than the original record source.
I would create a totals query that counts the drawings you want counted by the engineer field. Then, add this query to your report’s recordsource, joining on the engineer fields. This will expose the count field in your report’s fields.