Hello,
I posted a problem a little while back about a lookup field in a table
suddenly showing some columns as blank, for some clients, only.
Originally the mdb was shared by all, via a network folder. I created a
blank mdb and im****ted everything in the mdb into a this "blank" mdb and
created a client copy, for each machine with a link to the tables, and
based on advice from Allen Browne I downloaded a 2003 hotfix which dealt
with this issue, but it did not solve the problem.
While no new clients have shown this corruption, I'm stumped as to why
some clients show this problem, but not others. More info is:
1. you can click on the row in the dropdown, and while the info in the
drop down and key column shows as blank, it does appears after being
selected, in the table/column you want to drop it into.
2 the data is entered directly to the table and the lookup query is
simple, with no where statements, but I also created a form for the entry
and created an actual query to use, instead of a query string, but the
dropdown is blank, in the form...again, just on certain clients.
3. the relation****ps are fine and 1 to many referential integrity is
enforced.
I don't know where else to look, but given that the same original corrupt
clients continue to show this problem, I wonder if access holds some info
in a temp file, somewhere and this info is being used rather than fresh
info, much like how the pagefile.sys can hang onto corrupted info (I even
changed the registry to not keep this info on each loadup, but didn't
help).
Any ideas or direction or even similar experiences and fixes greatly
appreciated.
Thanks,
Alex
|
