Problem with Shared Workbooks crashing Access 2000.

  • Thread starter Thread starter Luke MacNeil
  • Start date Start date
L

Luke MacNeil

I've searched through some news groups and found alot of people that are
having problems like this.

The problem.

We have a master database that is replicated to another read-only copy.
The master only has one user. All others use the read-only copy.
The read only copy is shared so everyone can view the data.

At certain times, on certain computers we are unable to open the
read-only database. The workaround is to come over to another machine
(which happens to have admin rights) open and close the file, and then
it unlocks.

We're running netware, and I've read a microsoft technote that states
that novell has an update for this particular problem however I have had
no luck with it.

Any ideas?

Luke MacNeil
A+,Net+,Linux+,MCP,MCSA
 
Luke MacNeil said:
I've searched through some news groups and found alot of people that are
having problems like this.

The problem.

We have a master database that is replicated to another read-only copy.
The master only has one user. All others use the read-only copy.
The read only copy is shared so everyone can view the data.

At certain times, on certain computers we are unable to open the
read-only database. The workaround is to come over to another machine
(which happens to have admin rights) open and close the file, and then
it unlocks.

We're running netware, and I've read a microsoft technote that states
that novell has an update for this particular problem however I have had
no luck with it.

Any ideas?

Luke MacNeil
A+,Net+,Linux+,MCP,MCSA
Click to expand...
 
Have you tried copying the .ade or .adp file for the project to a folder on
the local c:drive and running the app from there? That fixes most multi-user
issues with access.
 
Hi, Luke.
We have a master database that is replicated to another read-only copy.
The master only has one user. All others use the read-only copy.
Click to expand...

Perhaps I misunderstand your setup, but it sounds like you've replicated a
database so that others can make changes to the data and resync the data
with the Design Master's data, but the data in the replica copy is
read-only, so _no_ changes are actually made in the replica copy. Am I
correct?
The read only copy is shared so everyone can view the data.
Click to expand...

To avoid problems in a multiuser environment, the database should be split
into a front end and back end. The back end should reside on the network
shared directory and contain the tables and relationships. A copy of the
front end, which contains all other database objects and links to these
tables, should be placed on each user's workstation, so that they can all
share the data. For more information on splitting databases, please see the
following Web page:

http://www.Access.QBuilt.com/html/gem_tips.html#SplitDB
At certain times, on certain computers we are unable to open the
read-only database.
Click to expand...

What method are these multiple users using to open the read-only database?
Are they using a shortcut that uses the command-line argument /RO? Is
user-level security applied to keep all of these users from making changes
to the database? If you are using the operating system's security
permissions to the database file and the directory where this database is
located, then many of the users will not be able to open the database. For
more information on methods to avoid these problems, please see the
following Web page for a link to the article, "Multiuser Databases":

http://www.Access.QBuilt.com/html/articles.html
The workaround is to come over to another machine
(which happens to have admin rights) open and close the file, and then
it unlocks.
Click to expand...

Not all of the database users have been given "Full Control" security
permissions on the directory where the read-only database is located.
Please read the article at the link listed above for ways to avoid this
annoyance.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
'69 Camaro said:
Hi, Luke.


Perhaps I misunderstand your setup, but it sounds like you've replicated a
database so that others can make changes to the data and resync the data
with the Design Master's data, but the data in the replica copy is
read-only, so _no_ changes are actually made in the replica copy. Am I
correct?
Click to expand...

Nope, thats not correct. We have one master that changes are made to,
that master is replicated to the read only copy, and the users opening
the read only copy only need to view the data. You are correct in no
changes being made to the replica copy.
To avoid problems in a multiuser environment, the database should be split
into a front end and back end. The back end should reside on the network
shared directory and contain the tables and relationships. A copy of the
front end, which contains all other database objects and links to these
tables, should be placed on each user's workstation, so that they can all
share the data. For more information on splitting databases, please see the
following Web page:

http://www.Access.QBuilt.com/html/gem_tips.html#SplitDB
Click to expand...

I will look this over this afternoon. In this particular case however,
I wont have the ability to restructure the database.. Corporate
politics you know. They just want me to make the error go away :)

What method are these multiple users using to open the read-only database?
Are they using a shortcut that uses the command-line argument /RO? Is
user-level security applied to keep all of these users from making changes
to the database? If you are using the operating system's security
permissions to the database file and the directory where this database is
located, then many of the users will not be able to open the database. For
more information on methods to avoid these problems, please see the
following Web page for a link to the article, "Multiuser Databases":
Click to expand...

This is exactly whats happening. The permissions are set on the folder
level on the Novell server. We recently added the create & delete
rights to that folder thinking that there was a problem creating and
deleting the .ldb files. So far there haven't been any reports of the
database not opening.
http://www.Access.QBuilt.com/html/articles.html
Click to expand...

I'll get on this link this afternoon as well.
Not all of the database users have been given "Full Control" security
permissions on the directory where the read-only database is located.
Please read the article at the link listed above for ways to avoid this
annoyance.

HTH.

Gunny
Click to expand...

Thank you very much for your time in replying. I appreciate it alot.

- Luke
 
[email protected] said:
Have you tried copying the .ade or .adp file for the project to a folder on
the local c:drive and running the app from there? That fixes most multi-user
issues with access.
Click to expand...

I'm not sure what those extensions are. I'm working with an .mdb file
 
Unfortunatly this problem was not resolved.. Users are still being
locked out of the file for no aparent reson. Full control over the
folder has been issued with no luck.

Any more ideas?

Thanks,

Luke.
 
Back
Top