Table rowsource lookup problem

Hi

Im having problems getting a column in one of my tables to display the
lookup values correctly.

The database is split, in the backend the rowsource for this
particular field is set to a query of another lookup table, this
correctly displays in a dropdown the values i want for that field.
However, in the front end the dropdown for this field is blank, when i
try to view the table in design mode to set the rowsource i get the
message: "this is a linked tabe with some properties that cant be
set", it then appears to allow me to change the rowsource and save the
table but the dropdown is still blank when viewed in datasheet mode.

Any ideas how i can get round this problem?
Thanks for any suggestions.
Paul

Re: Table rowsource lookup problem

On Oct 22, 9:51 am, "paulquinlan...@hotmail.com"
wrote:
> Hi
>
> Im having problems getting a column in one of my tables to display the
> lookup values correctly.
>
> The database is split, in the backend the rowsource for this
> particular field is set to a query of another lookup table, this
> correctly displays in a dropdown the values i want for that field.
> However, in the front end the dropdown for this field is blank, when i
> try to view the table in design mode to set the rowsource i get the
> message: "this is a linked tabe with some properties that cant be
> set", it then appears to allow me to change the rowsource and save the
> table but the dropdown is still blank when viewed in datasheet mode.
>
> Any ideas how i can get round this problem?
> Thanks for any suggestions.
> Paul

Paul,

If you are using lookup fields my advice is to have a form use lookup
tables instead. I agree with most posters here that data should be
entered through forms rather than directly into tables. If you
absolutely insist on using lookup fields, try going into the table
design in the back end where the actual table resides.

James A. Fortune
CDMAPoster@FortuneJames.com

Me: What are you doing in the table? What if you accidentally delete
hundreds of rows by mistake? Are you going to say, "No problem.
We've got a backup."?

Secretary: I've been going into the table to make quick edits for nine
years now and I've never had a problem.

Me: Nine years ago the tables weren't as interconnected as they are
now. You don't realize how badly you can mess things up by editing
the tables directly. You really need to use the forms like I told you
before.

Secretary: O.K., I'll do that, but the forms are much slower than
editing the table directly so you're going to have to put an update
query behind a button on the form so that I can update a huge set of
related jobs all at once.

Me: Sigh.