Sharing Database

[Gunti]

Hi,

I've created a database where people can fill in for example a postal code
whereafter access tells them which region this is, which people are
responsible, their phone numbers etc.

Now i have a question for improving this tool.

First: Currently it is located on a shared disk. If i have to update the
tool (as in add names, change layout etc.) i can not edit it because it is
always open on a computer. What i need is some kind of 'user control' where i
can kick users out of the tool (like shared excel documents have) when i want
to make a change. This so that people can link to the file, for example:
regiotool.mdb

When i create an update i just kick everyone out- update regiotool.mdb and
noone has to do anything. Right now i have to name the update regiotool 1.1,
1.2, 1.3 and send a mail to everyone to update their shortcuts.

 

[Clifford Bass]

HI Gunti,

You need to split your database. See
<http://www.granite.ab.ca/access/autofe.htm> for information about split
databases and how to update them. Also do a search for "split database" in
Access's online help.

Hope that helps,

Clifford Bass

 

[Larry Daugherty]

1. Your application should be *split* into a FrontEnd and a
BackEmd. The BackEnd must be in a shared folder to which every user
of your application has Full Rights.

2. Your FrontEnd should first be compiled without error and then
made into a MDE or ACCDE. Each user should have a copy of that "*DE"
on their desktop. Henceforth you will make changes to your *golden*
copy of your application and then compile to the "*DE" form you have
chosen and place the new version it its proper location (more about
that in #4 below). Users will no longer have the power to change your
design and cause untold problems.

3. The only instance in which you then need to deny your users
access to the BackEnd is when you are altering the design of the
BackEnd. Simple data updates should be automatic and transparent to
your users.

4. There are several ways to achieve the above but I particularly
recommend the Front End Updater concepts that you'll find on Tony
Toews' site. If you work your way through the FE Updater
implementation you'll have gone a long way to minimize the maintenance
burden for this and future applications.

HTH

 

[Albert D. Kallal]

I talk about developing and how you can modify your software while users are
working with the application here:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[Gunti]

A bit late, sorry. But thanks for the replies. I've figured it out

 

[Clifford Bass]

Hi Gunti,

Glad to hear it. You are welcome.

Clifford Bass