Self changing shared/exclusive setting?

A

Alp

Hi Experts,

I'm sort of puzzled to find out that my application (a FE/BE) is giving a
message to the second user that runs the FE indicating that "the DB is
opened by XXX Admin is put in a state ....."

I have not made any changes and no other person has done so either. What
shall I trace, look for or maybe replace? The app is on an NT server and
users run the app via a shortcut on their PC's. I found no *.ldb's left
behind, which I at first thought could be the culprit.

I'm stuck and would highly appreciate you valuable hints, advices.

Thanks in advance.

Alp
 
D

Duane Hookom

Do all users have full rights to create and delete files in the folder
containing your BE? They must be able to.
 
A

Alp

Yes Duane, they do. Actually there is nothing new on the app that was done
recently. It has been running without such problems so far. It will sound
typical but seemingly it "just happened today".

Since users who run the FE have their own Access installations, I do not
think that the runtime version on the server has any effect on how its run.
Actually I think there could be a corruption issue for the runtime version
and would also ask for your advice for possible repair (or re-install). But
it is only valid if one wnats to run it from the server itself and has no
functionality for regular users. Or am I terribly wrong in thinking like
that?

I will be taking over a fresh copy of the app (FE) to delete the old one and
copy it in place. But as I said, I should get the runtime version going
beforehand so I can try and see first hand if there actually is a problem on
the server.

I'll be grateful for any help you can offer as I'm quite tight and have to
get this corrected like yesterday!

Thanks,

Alp
 
A

Alp

Thanks Duane,

Well, situation is now solved. Was an interesting one though, at least for
me. One user mapped the server's drive on his PC and was running the
application from there. I reverted the shortcut back to the routine
\\server\directory\appname and the problem disappeared!

Still thinking of why?

Alp
 
Top