Hi Derek and Dmitry,
Thanks for understanding about the missing attachment.
Using a table for "two different purposes" as you describe... This is an acceptable practice though, right? Aside from the working solution, this is one of the indirect questions I was asking.
The part about being "not quite as straightforward" is this because of MVD specifically? Because I have dealt with similar situations in other software that I've used, but it can cause some confusion in larger projects.
I appreciate the example and as always your helpful replies. This will certainly provide me with more ideas as I learn MVD.
This is only a piece of a larger project, and I didn't provide any extra details about it. So it would seem odd to have each state listed as a neighboring state, but there is a reason for that...
I imagine that (this reason above) is something that could be handled within MVD itself, but my inexperience doesn't allow me to take that approach yet...
The larger project is for fleet management (vehicles traveling between the states). Each trip has legs which can represent any stopping point (even within the same state). The main purpose (excuse me if this is obvious) is for these boundary ComboBoxes to limit AND reduce the states presented to the user.
Thank you again folks!
"Energy and persistence conquer all things."