Hello Allen,
Thank you for the link. As for each having own front end, I mentioned I
did not split the db, per se, but rather created a blank db and imported
queries and reports, and then linked the tables to the main mdb, on the
server, and gave each client a copy of this "manual" front end - will
this not suffice? Is there a difference between this and the access
created split db or front end?

Also, the really really perplexing thing is why some clients show this
behaviour and others don't, even after the changes. Is something held in
cache somewhere, on the client?

Thanks,
Ax

"Allen Browne" wrote in
:

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