Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Queries / May 2005

Tip: Looking for answers? Try searching our database.

Renaming query column erases lookup's SELECT statement

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Bill Leddy - 23 May 2005 23:15 GMT
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.)?
Michel Walsh - 26 May 2005 18:22 GMT
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

> If you have a column in a query that has a lookup combobox specified, and
> you
[quoted text clipped - 10 lines]
> other
> development tools (VFP, Visual Studio, etc.)?
Bill Leddy - 26 May 2005 21:22 GMT
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,
>
[quoted text clipped - 24 lines]
> > other
> > development tools (VFP, Visual Studio, etc.)?
Michel Walsh - 27 May 2005 11:09 GMT
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

> Michel
>
[quoted text clipped - 53 lines]
>> > other
>> > development tools (VFP, Visual Studio, etc.)?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.