If the Listbox has its Multi-Select Property set to anything other than None, the problem isn't with Me....it's that the Listbox really has no Value Property, and since
Me.txtOffice = Me.lstDepartment.Column(1)
Me.txtBuilding = Me.lstDepartment.Column(2)
is trying to assign Values to txtOffice and txtBuilding, from lstDepartment, the code is going to fail. I'm guessing that since lstDepartment has no Value, the Access Gnomes, when executing the code, are simply using the data from Column(1) for both assignments.
Everything involving MVFs has to be done differently than it is done for traditional Fields, which is one reason most experienced developers shun their use.
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007