Rights

[Guest]

I have been working with Access97. While other people were using the DB, I
could still make programming changes without any problems.
With Acees 2003, while someone is using the DB, I am getting a message that
I have to open the DB exclusively to work on the DB. I need constanly to make
changes and I cannot ask the users to close the DB. Can someone help to get
around this ?

 

[Guest]

You would best off to split the databse ointo a front end and back edn
database. Then distribute a copy of the front ent to each users desktop.
This will allow you to continually work on your copy of the front end and not
have to kick anyone out. THen all you have to do is redistribute the
fron-end. There is a program that will allow you to do this it is called
Autoupdater and is put out by Granite Consulting http://www.granite.ab.ca/

HTH

 

[Guest]

This is by design. If I recall correctly, Access 97 allowed design changes
without having opened the database in exclusive mode. Access 2000 and later
does not allow design changes, unless you either open exclusively, or your
access can be promoted to exclusive use.

You really should split the database into a front-end (FE) and back-end (BE)
files. Each user should have their own copy of the FE database installed on
their local hard drives. Here are some reading assignments for you:

Database Splitting
http://home.bendbroadband.com/conradsystems/accessjunkie/splitting.html

Implementing a Successful Multi-user Access/JET Application
http://www.access.qbuilt.com/html/multiuser_applications.html

Tony Toews offers a tool to help make distributing updates less painful.
This is mentioned in the link shown above.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Douglas J. Steele]

There's no way to make changes to application objects (forms, reports, etc.)
if anyone else has the database open: it's been this way since Access 2000
due to the fact that Access does a monolithic save.

However, if you're running into the problem you're describing, it sounds as
though you haven't split your application into a front-end (containing the
queries, forms, reports, macros and modules) linked to a back-end
(containing the tables and relationships).

Only the back-end should be on the server. Each user should have his/her own
copy of the front-end, preferably on his/her hard drive. With that setup,
you can make changes to your copy of the front-end to your heart's content
without anyone else impacting you. Once you're satisfied with the changes,
you simply replace all the other copies of the front-end.

Tony Toews has a free Auto FE updater that simplifies ensuring that each
user has the appropriate front-end at
http://www.granite.ab.ca/access/autofe.htm

 

[Guest]

Split the database into front and back end files, the former containing the
forms, reports queries, modules etc, the latter the tables only (Access
includes a database splitter wizard for doing this). Put the back end on the
server and a separate copy of the front end (along with Access itself) on
each local machine. Assuming you first split it on your own local machine,
you'll need to refresh the links to the back end, using the built in linked
table manager, when you move the back end to the server.

You can then work on your development copy of the front end and simply
replace the front ends on each local machine periodically, which can be done
over the network. Any changes to the table definitions, and to the
relationships, will need to be made in the back end of course.

Ken Sheridan
Stafford England

 

[Guest]

Thank You all.
My DB is Split, but the FrontEnd is in the network. All Users use this
frontend. It is physically impossible to have the frontends on each user's
hard drive.
Guess I will work on a copy, and overwrite the DB on a weekend.
Thanks

 

[Guest]

hat is similar to what I do. I always have a developement copy that I work
on. That way I can always go back to an older copy.

 

[Guest]

Why do you claim that it is "physically impossible to have the frontends on
each user's hard drive"?


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Guest]

There is a compromise solution, which is to have the front end on each local
machine and Access installed on the server as well as the backend. I know of
at least one application of mine which is run in that way. I was surprised
at how well it performed in fact. All this needs is enough vacant space on
each local drive.

Ken Sheridan
Stafford England

 

[Larry Linson]

My DB is Split, but the FrontEnd is in the network.
All Users use this frontend. It is physically impossible
to have the frontends on each user's hard drive.

I am not certain why it would be "physically impossible" to have frontends
on each user's machine, but you significantly increase the chances of
corruption with multiple users logged in to the same front-end or monolithic
database. I am aware that there may be "policy" or "procedural" or
"logistic" difficulties with installing the front end on user's machines,
but those can usually be "dealt with" when management understands the
difficulties that can be caused by multiple users in the same copy of the
FE.

There are approaches, including the Auto FE Updater at MVP Tony Toews' site,
http://www.granite.ab.ca/accsmstr.htm and the one described in the article
at http://accdevel.tripod.com for handling the updating of user's copies of
FEs in a non-burdensome way.

Larry Linson
Microsoft Access MVP

 

[David W. Fenton]

There is a compromise solution, which is to have the front end on
each local machine and Access installed on the server as well as
the backend. I know of at least one application of mine which is
run in that way. I was surprised at how well it performed in
fact. All this needs is enough vacant space on each local drive.

Huh? What does Access being installed on the server have to do with
it? Unless you're running the app on Terminal Server, the apps
installed on the server are IRRELEVANT.

 

[David W. Fenton]

My DB is Split, but the FrontEnd is in the network. All Users use
this frontend. It is physically impossible to have the frontends
on each user's hard drive.

Then you shouldn't be using Access.