View Single Post
  #23  
Old January 15th, 2010, 09:59 AM posted to microsoft.public.access.tablesdbdesign
Keith Wilby
external usenet poster
 
Posts: 812
Default Lookup Field Issues

"esn" wrote in message
...
I have a lookup field in a table that is "text" data type and
restricted to values in the list. It works properly when entering
data, meaning it won't let the enterer remove the focus from the field
if the text they've entered isn't in the list. But for some reason it
will allow text values to be pasted into the field even if they aren't
in the list. I want to use the field to check for consistency in
preexisting data using copy and paste. In my experience this should
create a "Paste Errors" table with all the records having a value for
this field isn't in the lookup list. Any ideas why I'm not getting
paste errors in this case?


OK I'm just going to comment on your OP because I don't have the time to
read the reams of other stuff. If your goal is to correct errors in your
data before importing it then you could use a query with a join on that
field to a lookup *table*. That table would be a single field containing
permitted values. Use your query to return those records that do *not* exist
in the lookup table, correct the errors then run your import routine.

Keith.
www.keithwilby.co.uk