ChoonBoy,
Please cut and paste the entire code (procedure) you used in your next
reply.
Is the combobox "bound" to a field, or is it "unbound?"
*Upon re-reading your initial post*, I'm wondering if you're using this
"unbound" listbox to select a value, and use that value to locate a specific
record.
If that's true...
what is the value you are selecting in the listbox, and why is it necessary
that the listbox synch to the record you navigate to.
On my website, I have a 97 and 2003 sample file called Quick Find Combo
(combo would work the same as a listbox in this regard)
User selects a name from a combo, and that record is located. But, when
you manually navigate off that "found" record, the combo value (from the
last find) is still there. That's not a problem... that's how an "unbound"
field works. Whatever value is in the listbox, that value will remain...
until changed.
Let's say you select a CustomerID from the listbox, and find that
CustomerID record.
You could either...
1. Use the OnCurrent to manually force the listbox to show that's
records value.
Private Sub Form_Current()
Me.lstSelect = Me.CustomerID
End Sub
2. OnCurrent to Set the listbox to Null
Private Sub Form_Current()
Me.lstSelect = Null
End Sub
--
hth
Al Campagna
Microsoft Access MVP
http://home.comcast.net/~cccsolutions/index.html
"Find a job that you love... and you'll never work a day in your life."