"no valid fields can be found"

[prima854]

Kind of a strange problem, I'm trying to use the lookup wizard to create a
list box field on one of my tables and I'd like to base it off of another
table. When I choose the table I'd like to base the list off of, I get the
error "No valid fields can be found... please select a new source. There's
plenty of fields in the table to choose from so I'm not sure what could be
wrong.
Anyone have any suggestions? Thanks.

[Duane Hookom]

My suggestion is to not use lookup fields defined in tables
http://www.mvps.org/access/lookupfields.htm. Use combo boxes on forms.

Do you get similar issues with other tables/fields? Does the chosen lookup
table have a primary key, text fields, ....? Non-valid fields might be memo
or date fields.

--
Duane Hookom
MS Access MVP

"prima854" <prim...@discussions.microsoft.com> wrote in message
news:A99FBD7F-BD21-49F6...@microsoft.com...

[prima854]

Thanks, Normally I would just not worry about it and use other methods of
using lists, but it almost seems like an indication of a larger problem with
my setup or something. When I go to use the forms wizard to create a form,
none of the tables I have set up list any fields to choose from. All the
tables are listed, but when I select a table, no fields show up to choose
from.
All the tables have primary keys and text fields along with other fields
like number, date etc. They are all really simple tables as I've just started
putting them together.

[Duane Hookom]

You have some form of corruption that might require a re-install of Office
or possibly registering a DLL. This KB article might provide some additional
help http://support.microsoft.com/?id=303769.

--
Duane Hookom
MS Access MVP

"prima854" <prim...@discussions.microsoft.com> wrote in message

news:23CE3A07-3DC6-43EC...@microsoft.com...

[prima854]

Thanks for your help. Tried a bunch of different things, including this KB
article as well as lots of time banging my head on the desk, until I finally
stumbled on the solution, my anti-virus (Kaspersky) was preventing the
wizards from working correctly. It was at recommended levels, but those
levels were apparently affecting me negatively, so as soon as I set it to
stop monitoring VBA macros, Access began working the way it's supposed to.
Looks like it was working a little to well!
Anyways, thanks again.

[Duane Hookom]

Thanks for taking the time to reply back with the solution. It may help
someone in the future.

--
Duane Hookom
MS Access MVP

"prima854" <prim...@discussions.microsoft.com> wrote in message

news:89DC066B-773E-40AA...@microsoft.com...