Mar 01 2022 08:36 AM
Mar 01 2022 08:36 AM
It's been some time since I've worked in Access but I've been tasked with creating a database of certain features of our product (the easy part), and then creating a search form where users can search for one (or more) of these features.
What I've done:
1 - Created a table with about 40 checkboxes fields, as well as an autogenerated ID number and two short text fields for identifiers.
2 - Created a form where the user can enter the identifying information, as well as select multiple checkboxes, based on the features of our product (this is for data entry to populate the database)
What I need to do is create a form where the user can select one (or more) checkboxes and run a query to get a list of projects that have this feature(s).
I've created the query, but I'm unsure of how to get the results I want. I suspect I will need to have multiple IF; ELSEIF statements and do this in VBA. I have done this before, but I'm really struggling to remember exactly how it is done. I've looked at old databases, and still can't quite wrap my head around what I need to do.
Does anyone have any ideas; or need more information for clarification?
Thanks so much!!
Mar 01 2022 09:44 AM
Before investing any more time in this design, I strongly urge you to learn about Normalization, i.e. the process by which we design and create relational tables for a relational database application.
"...a table with about 40 checkboxes fields" is more like a spreadsheet and is the way many new developers start out, unfortunately.
Here is a link to a set of articles that describe the problem in more detail and also show you how to correct it. Later, when you have a proper set of related tables, you can return to the search task.
Mar 01 2022 10:08 AM
Thanks for this, but this isn't about relationships; I understand relationships and have developed many databases before. I'm just struggling with the wording for my queries.
We have a product that can have many different features - I won't get into details, but they are all unique. I could create 5 tables for the different product lines we have, but at the end of the day, I'm STILL going to have the same number of checkboxes for the features. They are all unique.
With reference to the article you posted, it's not like I have Item A and I'm looking for feature 1, 2 or 3. I am ONLY looking for features. They referred to patient names and symptoms; there is no patient.
I mean, yea, I could put the identifiers in a separate table, but at the end of the day, I'm still going to have 40 unique features.
I suppose, alternately, I could create multiple queries for each feature and the user would have to select which feature they are looking for. But that isn't really the path I want to go down.