Dear Angel:
If you do not reference all the columns by name in the query, the wild
card is the only alternative.
You can, however, build a form that would do this. In a form, it is
possible to reference columns from a query using subscripting. As you
do so, you can omit the column for password, either by name or by it's
constant indexed position.
The way I do it, the form would have a horizontal scroll bar. Certain
columns would scroll left and right, others (to the left) would be
static. These static columns would identify the record being
displayed. The column headings for these could scroll as well.
We use this to allow the data to be viewed and edited from a crosstab
query. This is often very useful for users. However, the data is not
permanently stored in this fashion. Rather, the crosstab query
creates a temporary table to be bound to the form. When the form
closes, the data is put back into the normalized form of storage,
after performing checks in case there are conflicts due to multi-user
changes to the data.
I mention all this because, other than the use of a temporary table
such as I describe, I know of no situation in which having a table in
which the number of columns increases would be good design. I do not
know, but can easily surmise from your post, that you may be adding
repetitive columns to the table. There is a good table design to
avoid this that will function much better, so much better that it is
nearly imperative you change your design to follow that.
So, it is my strong recommendation that you share the details of this
here so you can receive an explanation of a much better way to
accomplish what you are looking for.
Tom Ellison
Microsoft Access MVP
Ellison Enterprises - Your One Stop IT Experts
