coding for combo box problems - handling entries -

[Guest]

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 -

 

[pietlinden]

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 -

what does a duplicate value in your table have to do with a lookup?
Are you saying that you have a unique index on the field you're storing
the result of the combobox? Then you should change the rowsource to
eliminate "used" items. (just use an outer join or use the Find
Unmatched query wizard)

 

[Guest]

it doesnt have anything to do with dlookup. I mentioned dlookup because I
wanted to check for duplicate entries in my combo box before receiving the
"duplicate entry " error that is generated.

 

[Graham R Seach]

Trevi,

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

Regards,
Graham R Seach
Microsoft Access MVP
Sydney, Australia