Re: coding for combo box problems - handling entries -

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

The real problem here is you are using a bound combo box for searching.
Combos used for searching or filtering should not be bound controls. This is
the behavior exhibited when you use a bound control for searching or
filtering.
--
Dave Hargis, Microsoft Access MVP


"trevi" wrote:

Thanks Graham. I will use it. But, what if somebody does something silly
like trying to delete a value in the combo box and then trying to move off
the control. Then the error generated is "index cannot be null". What can be
done then ?

"Graham R Seach" wrote:

Trevi,

Try this:
http://www.pacificdb.com.au/MVP/Code/NIL.htm

Regards,
Graham R Seach
Microsoft Access MVP
Sydney, Australia

"trevi" <trevi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2C375450-9C88-4A62-8FDA-3CE088492F08@xxxxxxxxxxxxxxxx
I have my combo box working fine except that when testing it , I found that
if I enter a value that alrealdy exists, an error is generated about
duplicates. I tried doing a dlookup for that problem. It's not working
yet,
but is this correct idea?
Also, if I try to delete my entry from the combo box, i get stuck in that
field because it thinks it's a null value. In that case, what's the best
way
to handle that kind of situation?
thanks -



.

Relevant Pages