Forum Discussion
Combobox goes empty on new record
- It's not the only way to handle the situation. However, it is the appropriate way for a relational database application.
Show us the SQL from the row source for the combo box.
Show us the SQL from the record source for the form.
Is the form in Datasheet view, Continuous view or Single Form view?
thanks for your reply.
The form recordsource is: SELECT * From Policies
The rowsource for the combobox is:
SELECT Policies.Risk_Name
FROM Policies
GROUP BY Policies.Risk_Name
ORDER BY Policies.Risk_Name;
It's a Single Form.
Ps the control is linked to Risk_Name too
- Do you not have a look up table for "Risk_Names"? That would be the normal approach. This approach sort of works, but has the unfortunate side effect observed.
- hmm do you mean creating a "lookup wizard" in the table design for that column? If so, not sure that works with a dataverse back end?
No, I mean a second table called "Risk_Name". It is a "Lookup Table" because it has only the values you need for "Risk_Name". You use Lookup tables to provide a closed list of possible values for "Risk_Name" which you control. It limits users to only those values provided in that table. What you are doing actually allows for any previously entered value to be repeated, whether it is appropriate or not because it is based on the values already in that field in the Policies table. Once a value is entered, it continues to be offered.
Lookup tables are standard Access design. Dataverse is designed to make it more opaque what is going on, but the same concept is available there.