Why do you have one-to-one relationships between the tables?
Why does the ALL table have User and PC fields?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
I have an issue with Form fields. I've created form, added fields from 3 different tables and I'm not able to edit any field. My relationship looks like this:
My form with not updateable fields:
Please note, that if I put fields from only 2 tables (for example ALL and TEL), everything was fine. I was able to edit it and save changes. The issue appeared when I've added another field from USERS table. It's probably something very easy, but I don't get it.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Why do you have one-to-one relationships between the tables?
Why does the ALL table have User and PC fields?
It's just an example :) PC and User fields are not importnat in ALL table. 1to1 is required for unique values. I don't want to have any duplicates.
Hi Righto,
Can you tell us what you are attempting to model with this table structure? What's the scenario?
General idea is to create form where all data from many tables would be editable. Like Table1 (Software) Table2 (MobilePhones) Table3 (Laptops) etc. to be in one single form to edit and save changes. I want to create a form with all date assigned to 1 user. For example Richard is having this laptop and this mobile phone and this software on this laptop with this bitlocker key installed etc. But when I put data from more than 3 tables, than access is blocking this form from editing data. It was all good with 2 different tables on 1 form. I know I can modify tables and put everything inside one table, but it's not a solution. I have no idea why MS Access is blocking me from editing those rows.
The typical solution is to create a main form based on your user table where you can maintain only attributes about a user (not software or hardware). Then create subforms for the other related/child tables and add these subforms to the main form. You would set the Link Master/Child properties of the subform controls to the user table primary key and the user field in the related tables.
Lots of times you will see the subforms added to separate tabs on a tab control.
Your tables should allow multiple records in the child tables for the same user.