Access Terminal Sever

[Guest]

I have people using remote desktop to log in to a terminal server and use MS
Access. The problem im having is they cant open the database if someone else
has it open. I know this is possible because it was working before this
server crashed. Thanks for the help.

 

[Arvin Meyer [MVP]]

I have people using remote desktop to log in to a terminal server and use MS
Access. The problem im having is they cant open the database if someone else
has it open. I know this is possible because it was working before this
server crashed. Thanks for the help.

The only way I know to successfully run Terminal Server and Access without
corrupting the database files is to have a separate copy of the front end in
a user's folder for each user. I succesfully run a Terminal Server with up
to 18 users and I know of sites with twice that many.

I have a batch file which allows any user with permissions in the database
group to create a folder and download each database he/she has permissions
on at their first login to the Terminal Server. Subsequent logins download
and replace that front-end so that they always have the latest copy and they
never need to worry about compacting.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

 

[Tony Toews]

I have people using remote desktop to log in to a terminal server and use MS
Access. The problem im having is they cant open the database if someone else
has it open. I know this is possible because it was working before this
server crashed.

This is probably a permissions problem on the directory in which the
backend is installed. The users must have create/delete privileges
to that directory. What is happening is that Access can't create the
..ldb file which allows multiple users to update the MDB. So Access
only allows one user at a time.

One simple way of testing this is to ensure the users can create and
delete a file in the network share. Any file, even using notepad, is
enough to test this. I simply don't trust all those permissions screen
within the OS. You never quite know whats lurking behind the advanced
button. So test this yourself.

Sometimes it could only be one user who does not have create
privileges to cause problems who just happens to be the first user
into the MDB at that moment in time. Then all the other Access users
can't access the file because the first user is in exclusively.

"I found that I could keep the permissions set to Change, but had to
ensure that the directory in which the db resides was set to not
inherit permissions from it's parent. It seemed that every time a new
user logged onto a given machine, it got messed up."

See ACC: Determining Which User Has Opened Database Exclusively
(Q169648)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q169648
Essentially you must use tools on the server to determine who has
locked the file.

For MS info see ACC: Introduction to .ldb Files (95/97) [Q136128]. Or
the version appropriate for your version of Access.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Guest]

The users on terminal server can create new files. I think that it is a
setting on the server itself that isnt right.

Scott

I have people using remote desktop to log in to a terminal server and use MS
Access. The problem im having is they cant open the database if someone else
has it open. I know this is possible because it was working before this
server crashed.

This is probably a permissions problem on the directory in which the
backend is installed. The users must have create/delete privileges
to that directory. What is happening is that Access can't create the
..ldb file which allows multiple users to update the MDB. So Access
only allows one user at a time.

One simple way of testing this is to ensure the users can create and
delete a file in the network share. Any file, even using notepad, is
enough to test this. I simply don't trust all those permissions screen
within the OS. You never quite know whats lurking behind the advanced
button. So test this yourself.

Sometimes it could only be one user who does not have create
privileges to cause problems who just happens to be the first user
into the MDB at that moment in time. Then all the other Access users
can't access the file because the first user is in exclusively.

"I found that I could keep the permissions set to Change, but had to
ensure that the directory in which the db resides was set to not
inherit permissions from it's parent. It seemed that every time a new
user logged onto a given machine, it got messed up."

See ACC: Determining Which User Has Opened Database Exclusively
(Q169648)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q169648
Essentially you must use tools on the server to determine who has
locked the file.

For MS info see ACC: Introduction to .ldb Files (95/97) [Q136128]. Or
the version appropriate for your version of Access.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Tony Toews]

The users on terminal server can create new files.

Please be more specific. Can your users create and edit files on the
server in the same directory in which the backend resides?

Tony

--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm