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?
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Ax" wrote in message
...
Hello Allen,
Yes for the manual split, and thanks for that tip, too (manual vs. wiz)!
All clients are 2003, but they were connecting to and sharing the same
Access 2000 mdb.
The 2003 clients didn't see this problem right away: 1 showed it with one
table, then a week later the second client showed it with the same table,
then the first client had a problem with another table, and then that's
when I created and gave each their own client, and upgraded the main mdb
to 2003. Now I'll go back and do the hotfix.
But the really strange part is that I changed the lookup query string to
use a query, but rearranged the columns for the the output, but the
corrupt clients now don't show that blank lookup field, at all...which
makes me think the corruption maybe in some sort of cache or temp file in
the client? Just for my own curiosity I may try a scan of the hard drive
using something like win-hex - using different strings to search
for...maybe useless but it'd be interesting to see if anything turns up.
Thanks, again!
Ax
"Allen Browne" wrote in
:
When you created the blank db, linked the tables, and imported the
other objects, you gave each user a separate copy of this front end?
If so, the result is the same as splitting using the Wizard. (In fact,
that's the way I do it rather than use the wiz.)
I'm guessing that the A2003 SP3 machines are the ones that have the
problem. The A2000 users the A2003 users who are on previous service
packs probably don't exhibit the issue.