It sounds like you've based your dropdown validation on data in the same sheet as the source text, something that only works in a single sheet.
If you use a named range (look at the Name Manager in the Formulas ribbon)and source your validation as the name of your range
i.e.
=YourRangeName
I'll give you some clues:
1. Table design. I modelled your many-to-many relationship between substances and health risks via a junction table.
2. A subform (in data sheet view) bound to the junction table, and placed on the form bound to the substances table.
3. Linking between the form and...
Right, back to basics....
A table is where the data is stored. It contains only the data that it needs to help. It usually represents an entity of your business. ALL information in the fields of that table should be dependent on your primary field (your unique identifier). In these cases, I...
Look at qryEvents in the sample. It has a field that I mocked up called ShowName2. It does what you want. Because, in the events table, you have the show name and you have the event dates, you have greater flexibility.
Hopefully you are using a form to enter this stuff into your ledger.and not...
You only need the ID. The relationships in the database allow you to join between the tables, using these keys, to get the data from other tables.
Do you take your own tables of that size to fit a booth, or is that the size of the booth you request at the events? If the latter, then it's more...
My point #3 was table design, not VBA. Best to get table design locked in before moving on to queries and forms, never mind VBA.
What is a register of substances? Your database or the table? I think the database is the register and I think the table contains substances and information...
Which of the fields returned is your users' environ code: 0, 1, 2, or 3?
Just a basic DLookup() would get you the information from tbl_Users with the environ code as criteria.
eg
UserName = Nz(DLookup("Forename", "tbl_Users", "EnvironCode = """ & rs.Fields(??) & """")) & Nz(DLookup("Surname"...
Looking at your sample database, I'll point out the following....
1. Get in the habit of using prefixes for your objects. So, rather than Supplier, use tblSuppliers; a) because adding tbl lets you know at a glance that are referencing a table; and b) it's a damn good practice. Then, if you...
Yeah, that's NOT the way to go. The reason? If there's only 1 health risk, that's three columns blank and wasting space. If there's a need for a 5th health risk, then you have to add a new field, amend all queries referencing this table, amend all forms referencing the table, amend all reports...
One other thing I would suggest, looking at your relationships, is the possibility of extending your table design...
What I mean is that you are assigning only one health risk to a substance. Is it feasible that health risks to substances is actually a many-to-many relationship, in that one...
You would need to use VBA on the combobox's OnNotInList event.
Effectively, when the event is triggered, you would open up your Supplier admin/data entry form, and get the user to enter the details. Then you return a value to the event of Response = acDataErrAdded to indicate that the value is...
Looking at the database, it looks like you may need some initial tables like this, and then more to model the financial parts, as I'm not sure how they all inter-relate...
An Events table. This table will represent the many events that your business will handle/present. Not to be confused with...
On a train now, so can't open database on iPad, but you can look into either Domain Aggregate Functions (DMax, DMin, and DAvg). Or you can calculate Min, Max, and Avg in your queries.
Where it says Group By, you can change to a calculation method.
Forms to add. Otherwise, correct.
You have a table for each entity you are required to model. Sometimes, you may even need extra tables to model a many-to-many relationship.
That's what spreadsheets are for. If Access was like Excel, we wouldn't need Access because, as the kids say, there's...