First Glance Solution (not recommended)
What it Was
My initial reaction to this problem was to try and use a change event. Setting up subroutines for each combobox to change the value of the other combobox would have then been the solution.
Why you shouldn't use it
However, in the documentation for the Access vba change events (link above) it clearly states:
"Avoid creating two or more controls having Change events that affect each other — for example, two text boxes that update each other" (msdn access vba change event)
Unfortunately, this is exactly what you would be doing using the change event solution (using comboboxes instead of text boxes). In your example, a change in the ComboID combobox would trigger the appropriate change in the ComboName combobox, but that change in the ComboName combobox would trigger an attempted change in the ComboID, and this loop could continue on. Therefore, this is not a good answer to your problem.
A Better Solution
An AfterUpdate Event appears to be the more appropriate approach to use in this case.
Why the problematic loop won't be triggered
As mentioned in the AfterUpdate documentation:
Changing data in a control by using Visual Basic or a macro containing the SetValue action doesn't trigger these events for the control.
Therefore, an AfterUpdate Event (possibly using a SetValue) should be a much better approach.
Much thanks to @Remou for pointing out the error of my change event ways and bringing the AfterUpdate event to my attention.
