What you are describing sounds like a known problem with Access 2003 Service
Pack 3. Details:
http://allenbrowne.com/bug-Access2003SP3.html

As the article explains, you will want to download this fix from Microsoft:
http://support.microsoft.com/kb/945674

If different users are opening the database at the same time, you may want
to consider splitting it so everyone has their own separate front end, but
tehy link to the same shared data. If that's a new concept, see:
http://allenbrowne.com/ser-01.html

--
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.

"Alex" wrote in message
...
Hello,
Hoping someone can help because haven't been able to find info online,
and it's driving me crazy, and please bear with me thru the background
info, as I'm trying to cover as much background info as possible.

An access table was setup so that everyone (5 or 6 users) was opening the
same mdb, via a shared folder on a server, and they had 2003 on their
machines but were connecting to and opening an A2k mdb file.
The problem started with 1 machine and spread to 1 other, but had not
affected all others, yet.

The problem was that users would open a table, and there was a
lookup/dropdown, with a query string to another table, pulling approx 4
or 5 fields. One day the bound field was just blank. The other fields
and all other data in the db shows up fine, but just not this one field.
The field is there, but it's blank.

I did a repair, but no effect. I loaded 2003 on the server, ran the
latest Jet update, created a blank mdb and turned off things like auto
correct, etc. and imported all of the objects. I didn't split the db, per
say, but I went to the client machines and created a blank db, turned off
the reccomended default settings, and imported all of the queries and
reports, and linked the tables.

The client machines with the corrupt or missing lookup still showed the
same problem. Instead of a query string, I created a query and changed
the order of the fields, and pointed the lookup at this query - this time
the field did not even show up, in the dropdown fields

Again, some machines are fine, but the machines with the original problem
still exhibited this problem.

Is there any info stored in cache on the client? should I delete the
page.file?

Should I have actually split the db, or was creating a new mdb and
brining everything in, and linking the tables the same? I didn't split
it because I wanted to turn off the default settings, and thought that
importing everything and linking would have the same effect.

Has anyone every seen or heard of such a persistent problem?

Any help or info greatly appreciated.
Thanks,
Ax