Networked Access database won't work on all machines

[vacant]

I have a read-only Access 2000 database that’s on the ‘public’ drive on a network. This db is mainly used as a directory but also to print lists and the occasional mail label. Therefore I would imagine - although being relatively seldom queried - there is likely to be several instances of it open simultaneously.
The problem is, of the 100 or so machines in the building, whilst it works perfectly on the majority, on a significant few it just won’t play the game.
It's always the same: the user launches the thing and makes his/her selection via a list box, and hey presto the correct record is returned. After that the trouble starts. Whatever the user selects from the list, the record just doesn’t change, and I stand there looking like a right plant-pot on the end of another withering look before shuffling away muttering that I’ll look into it whilst not really having a clue where to begin.
So that’s where you people come in, I hope? Any ideas?

 

[JeremyNYC]

Terry,

You'll have to post significantly more information for us to help you. I will say you don't want to have people actually using a database that's only stored on the network. People should be opening a copy that gets placed on their machine.

That said, you'll want to post back here with the code, sql, events being used when this thing goes wrong, so that people will be able to see where the error is.

Jeremy =============
Jeremy Wallace
Designing, Developing, and Deploying Access Databases Since 1995

http://www.AlphaBetCityDataworks.com

Take a look at the Developer's section of the site for some helpful fundamentals.


Remember to reward helpful tips with the stars they deserve.

 

[vacant]

Thanks Jeremy
I didn't post any code here because I am fairly confident that's not where the problem lies. You see the thing works *perfectly* on 95% of machines, you can sit there all day searching and printing all you like and it will never let you down. It's just on these handful of others it refuses to co-operate.
I tried the splitting idea you suggested but that only served to slow it down as well as not function.
Thought it might be a network problem but I've been able to test it today in the knowledge that no-one else had it open, and still it was the same.
Think I'm gonna ask ICT to do a reinstall of Access on these machines.

 

[lameid]

Do all users of the application have the same file permissions to the database?

Are you using Jet? If not, what is your back-end?

What NOS is in use (Win 2k, Nt4, Novell, Linux)?

How does the drop down make the list change? Is it the bound 'field' of a sub form? Does it have an afterupdate event that finds the record? If the latter, the code may help someone answer your question.

Is everyone running Access 2000 or are some running Access 2002 (possibly related to last question)?

Are there any missing references on the machines that do not work? If so, is the reference needed for the database or can you remove it?

 

[vacant]

thanks a lot for the suggestions, however i've just found the answer here....and guess what, it's another bug. the problem machines happened to be those running 2000 sr-1

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q269380

it does work, but it also slows the form down a little. i wasted 2 days fretting over my code before i found this. it's just not good enough really, if i see that bill gates i'm gonna wring his scrawny neck

 

[JeremyNYC]

Hmm. Good to know about that. Glad your pain (if not your users' pain) is over.

Jeremy =============
Jeremy Wallace
Designing, Developing, and Deploying Access Databases Since 1995

http://www.AlphaBetCityDataworks.com

Take a look at the Developer's section of the site for some helpful fundamentals.


Remember to reward helpful tips with the stars they deserve.