Forum Discussion
Solved
Combobox goes empty on new record
Hi all - silly issue that somehow I can't get the answer to. Any help is appreciated. I have an Access database (dataverse backend). I'm using a data entry form, which works well. There are a varie...
- It's not the only way to handle the situation. However, it is the appropriate way for a relational database application.
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.
ah I see, you mean simply a related table with those unique risk name as values? Yes that would be better from a design perspective. Initially this field started live as a sort of free type field , later on with some grouped functionality on the risk name.
If that's the only way around it I may have to do that indeed. Bigger implementation job than planned. There's no other hack you can think of?
If that's the only way around it I may have to do that indeed. Bigger implementation job than planned. There's no other hack you can think of?
- It's not the only way to handle the situation. However, it is the appropriate way for a relational database application.
- You're absolutely right. I was implementing a short cut that would have resulted in long term pain. I created a table for the risk names.