Renaming query column erases lookup's SELECT statement

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

If you have a column in a query that has a lookup combobox specified, and you
try to add or change the name of that column in the result set (not the value
or expression for the column), the select statement specified for the lookup
combobox is lost.

This also happens if you try to modify the column name directly using the
SQL view.

Is there a specific place to report Access bugs like there are for the other
development tools (VFP, Visual Studio, etc.)?
 
Hi,


The "lookup" is a kind of formatting supplied by Access, but if you "change"
anything, the tracking is lost, indeed. You can FORCE the lookup to occur by
specifying an INNER JOIN, which is much more robust (and not that much
harder to built).


SELECT a.*, b.FieldWIthResult
FROM a INNER JOIN b
ON a.lookup = b.lookingInto



Hoping it may help,
Vanderghast, Access MVP
 
Michel

I think you are telling me to join to the other table to display some of
it's columns, but actually I'm using the lookup to support a foreign key
contraint and limiting the user to valid keys from the other table. It also
helps when you can show the name of the item instead of a record ID number
when the user is creating the linkage. You can't show the data from the
other table until you have the pointer (foreign key) set.

Really this problem is only a minor annoyance, but I was hoping to report it
so maybe Microsoft could fix it in a future release. It's frustrating to
have your work trashed without warning. They may or may not fix it, but if
nobody tells them they won't fix it for sure!

If you go to the MSDN Product Feedback report bug page, they list most of
the other development tools. I was wondering if there was another page
specific for Access, because Access does not appear in that product list.

Thanks for your help.

Bill
 
HI,


I am not sure Microsoft will consider it a bug, but "by design". You can
probably reach whatever concern Access by first accessing "Office", since
officially, Access is part of Office, and not an independent product (like
C#).


If you want to enforce presence in another table, use a relationship and
enforce it (take a look at the Relations Window). Alternatively, use a combo
box and 'Limit to list".



Hoping it may help,
Vanderghast, Access MVP
 
Back
Top