View Single Post
  #7  
Old June 18th, 2008, 04:35 PM posted to microsoft.public.access.tablesdbdesign
Ax[_3_]
external usenet poster
 
Posts: 1
Default A2k lookup field corrupt on some machines

Hello Allen,
I don't think this is possible, as the query is just a straight "select
x, y, z from abc"

As well, data is returned in that column, by the clients who were not
"bitten by the bug" and still continue to show the info in that column,
even with my new client mdb - it's just that the clients who suddenly
lost showing that info, continue to not show it. I will apply the hotfix
and let you know if it reappears, but it's just so strange...

Thanks, again!
Ax


"Allen Browne" wrote in
:

There's another valid reason why a combo might display as blank, even
though there is a value in the underlying field.

Say a combo has 2 columns: ClientID and ClientName.
ClientID is zero-width, so it shows the client name.
Now you set the RowSource to:
SELECT ClientID, ClientName
FROM tblClient
WHERE (tblClient.Inactive = False);

Now consider a row where the ClientID is an inactive record. In this
case, the ClientName is not in the RowSource query (because of the
WHERE clause.) So there is nothing for Access to display, even though
there is a valid ClientID.

Is that kind of thing possible in your database?