sharing through Network

R

Ruud

I have developped an application in access which runs on a network. We have 8
users sharing this database. I have split the application with the database
and linked the flies from the database to the application.
While everbody is already working with the application, we still come
accross issues which needs to be changed, both in the tables as in the
reports. When I would like to make these changes I get a message that I don't
have exclsuive right and therefore I'am not able to ammend anything. Is
there a way to close out users or have the possibilty the make these changes
without closing the application on the workstations which run the apllication?
Your assisntecen is appreciated.
Kind Regards,
Ruud
 
S

SteveM

If you try to open it by double-clicking on the file icon you will not be
able to open it if users are already have it open. If you open Access first
and then open it from there you should be able to make your changes. However,
you will not be able to make changes to tables that are currently being
edited by a user. In any case, it is strongly recommended that you do your
changes when all users are out of the system.

Since your reports are in your front-end, you should be able to make changes
and then roll out the changes to your users. Each user should have a copy of
the front-end on their machine not share it on the network.

Steve
 
K

Klatuu

In addition to SteveM's comments, You don't modify the production copy of the
front end. You have a development copy to work on. You should also do your
developement using a copy of the back end. You don't want to spaze up
production data.
The only issue you have is redeploying the applcation after you have
completed your changes. There are a few ways to do this.
Going from worst to best:
1. Tell all the users to copy the new mdb(3) from a shared folder.
2. Tell the users to run a .bat file that deletes the old version on their
computer and copies the new one to their desk top
3. Find or write a front end updater. I would send a link, but I can't
seem to find it.
The basic concept is to have a version number in a table in the backend and
a table or property in the front end that shows the current version.
In your startup code, check to see the version number in the front end
matches the current version number in the back end. If it does, carry on.
If it does not, start the updater and quit you database. When the updater
launches, it renames the current front end on your computer to a different
name and copies the new verison of the front end from a specified location on
the server to your computer. Then it launches the new version of the front
end.

To make it work, you change the version number in the back end.
 
Top