Problem opening shared access backend

[Brent]

Hello,

I have an Access 2000 app that is split into a backend data file and a front
end.

I have set up terminal services for remote users to log in and open the
access front end on the terminal server. When the access front end is opened
some code runs that opens a connection the backend.

Some TS users can open access without a problem but some get a message
saying the backend is already opened exclusively. If I navigate to the
backend mdb while logged in as a user with the problem and try to open it
directly I get an error saying the database file cannot be found even though
I'm looking right at it!

It has to do with the TS user account not the access user account. When
logged in as a TS user that can successfully open the Access file any Access
user login will work. When logged into TS as a user who cannot open Access
none of the access user accounts will work.

But it also has to do with Access in that only the backend mdb cannot be
opened by the problem TS users. They can open other nonshared access files.
In fact they can open the front end (after a series of errors) to the shared
backend they just can do any work because they have no data.

I have checked the user accounts on the 2003 server but cannot find any
differences between those that can open the access back end and those that
can't.

I have Access 2002 installed on the Windows 2003 server but the Access app
and back end is in 2000 format.

Thanks for nay comments.

Brent

 

[Brent]

RE: Problem opening shared access backend

er..I mean thanks for ANY comments.

 

[Brent]

Solved -RE: Problem opening shared access backend

Solved -RE: Problem opening shared access backend

OK, found the problem.

The backend MDB only had permissions for administrative users. Some TS
users were members of the admin group and some not. I gave the Users group
permissions on the mdb and now al can use it.

Brent

"Brent" wrote:

> Hello,
>
> I have an Access 2000 app that is split into a backend data file and a front
> end.
>
> I have set up terminal services for remote users to log in and open the
> access front end on the terminal server. When the access front end is opened
> some code runs that opens a connection the backend.
>
> Some TS users can open access without a problem but some get a message
> saying the backend is already opened exclusively. If I navigate to the
> backend mdb while logged in as a user with the problem and try to open it
> directly I get an error saying the database file cannot be found even though
> I'm looking right at it!
>
> It has to do with the TS user account not the access user account. When
> logged in as a TS user that can successfully open the Access file any Access
> user login will work. When logged into TS as a user who cannot open Access
> none of the access user accounts will work.
>
> But it also has to do with Access in that only the backend mdb cannot be
> opened by the problem TS users. They can open other nonshared access files.
> In fact they can open the front end (after a series of errors) to the shared
> backend they just can do any work because they have no data.
>
> I have checked the user accounts on the 2003 server but cannot find any
> differences between those that can open the access back end and those that
> can't.
>
> I have Access 2002 installed on the Windows 2003 server but the Access app
> and back end is in 2000 format.
>
> Thanks for nay comments.
>
> Brent