Search results

I am not sure if normalization is really the problem as much as consolidation if that is a term. For example you commonly see people build a table of Customers, Suppliers, etc.. Or a different table for different types of contacts. Sometimes these tables often have the same fields or nearly...

You kind of missed the point. The relationship diagram is invaluable if you use it to enforce referential integrity. It has very limited value if not. Then you have default joins but no way to enforce data integrity.

OMG! There is no teaching anybody anything. There is nothing for the user to do. You just set the rowsource of your different lists based on a query.

FYI, you do not have a relationship diagram, you have an image of default query joins. There is no referential integrity enforced on any of those relationships. So what's the point? This diagram only serves to set the default join type and all are inner joins.

Access has this cool thing called queries. You should give them a try. "Select * from tblSymptoms where condition = 'diabetes'" Provides a list of only diabetes symptoms to use as your rowsource. or "Select * from tblSymptoms where condition = 'dementia'"

If the references tables are not editable and you manage what goes in the lists, then the reference tables could stay in the front end but then you cannot enforce referential integrity. I then would then keep the source reference tables in the front end, but when the user gets a new front end it...

You can send email, snail mail, or use another file sharing app if you like.

Not everyone needs a split db, but your specific scenario warrants it (almost. If the tables were settled). 1. You absolutely need to split a db if you are in a multi user db where people are simultaneously working with the same data. 2. Or where you want users to be able to work on their...

Then it is perfect to move them all into a single lookup table. Way easier to manager.

In the mean time you can simply delete out all the data and send me the empty db. I can at least see the forms and proposed tables. The relinking is not an issue as long as your users always put the BE in the same location as the FE. That is easy to ensure. You have an application Folder and...

@DakotaRidge, No problem, I already solved that issue. When ready I will send to a link to a google drive where you can upload the database, and I will start to slowly whittle it down. Just delete the sensitive records using the provided code. To make it understandable you need to leave in...

The other thing I will do when you send me the database is to combine the rest of the tables I see into a single Expenses table. Pretty sure most ERP do not have an expense table for doctors, car repairs, restaurants. So from your image I will end up with two maybe three tables. Heck I have 17...

About 80% of that image is lookup tables. As I said when you send me the db I will crush them all down into one single table.

I make one form and load the images dynamically. Something like this where you can show multiple ship floor plans and "geo locate" tasks to complete. https://www.access-programmers.co.uk/forums/threads/user-made-command-button-that-can-be-moved-with-mouse.329403/post-1897600

One way I would get rid of a lot of tables is to combine all the MVF lookup tables into a single lookup table. This demo is a bunch of single select comboboxes, but the same would work with MVFs...

I have posted thousands of examples of access databases, queries, and code examples. Just start searching. How about you post 1 real database example? These are kind of health and medicine related ones...

Not true. I solved this a long time ago, but lost in the noise. FYI. I wrote none of this code, and let AI do it. 1. Add an Is_Sensitive field to all tables so that you can mark records as sensitive. Sub LoopThroughUserTablesAddSensitve() Dim db As DAO.Database Dim tdf As DAO.TableDef...

Send me your database, and I promise you I can reduce it by 95%. PM me and put it in a google drive. Since it is so poorly designed I may struggle to make heads or tails of it initially, but I am confident I can radically reduce it. I may have exaggerated. It may take 40 tables and forms max...

Sounds to me you need to write the books, because I have never seen these topics addressed anywhere as being important in database development. For your development: "Designing Access Applications for Different Personalities" "Race based Access Database Design and Development" sounds...

Have you looked at the Demo? As you asked the demo shows multiple ways to select multiple values and store in a normal junction table. The subform and pop up have checkboxes. The multi select does not. The crosstab uses just a click. The specific MVF controls only work with MVF fields and...