Stop Access 2k from adding columns to query datasheet view 2

[ESquared]

I like being able to define lookups for various columns in my tables. It certainly helps when I am first creating my database and don't have any forms yet, and it helps at any time when viewing tables directly. It makes simple data entry possible through table datasheet view.

However, when I write a query and I ask for the WhateverID:

[tt]SELECT WhateverID FROM MyTable[/tt]

then go to query datasheet view, I most absolutely am not interested in "help" such as getting the lookup value in this column, or the alternate column name, or an extra column. I'll do the censored join myself if I want that. I need these queries to preview what's going to be happening in my code and/or forms.

Is there any way to cope with this short of never defining lookups for columns in my tables?

I'm not quite sure how the extra columns are created, it definitely is related to doing things in "Query Design" view rather than in "SQL Design" view. Extra columns seem to be "remembered" in the query design, so even if you temporarily put in the text of another query entirely and view that, then switch back, the extra columns come back. Only by defining a new query with the same query text was I able to get the blasted extra column to vanish. But then one of my WhateverID columns is again displaying lookup values instead of numbers.

 

[dhookom]

Un-define your lookup fields in your table designs. Use forms with combo boxes for data entry.

Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]

 

[lespaul]

just as a basic rule of thumb you should never define lookups for columns in your tables.

The Evils of Lookup Fields in Tables

Leslie

 

[ESquared]

I think I already concluded that lookup columns in tables is just a bad idea.

Thanks for the input.