Explaining to users why database has been split

[forest8]

Hi

To allow the possibility of multiple users, I will be splitting my access
database.

How do I explain the logic of splitting a database to users who are not
access-savvy?

Some of the questions I anticipated are:
Why did you do this?
How does affect me if I'm working offsite?
How does it work?
How will it update the data?
Etc.

Is there any place that I can read up on this subject?

Thank you in advance.

 

[Gina Whipp]

forest8,

This should help... (Plus, plain English answers that I have used below)

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

http://allenbrowne.com/ser-01.html

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Hi

To allow the possibility of multiple users, I will be splitting my access
database.

How do I explain the logic of splitting a database to users who are not
access-savvy?

Some of the questions I anticipated are:

Why did you do this? ***To prevent corruption and error messages. Like two
people with keys to one car. The first one gets to go for a ride, the
second one gets stuck at the side of the road with keys in hand...

How does affect me if I'm working offsite? ***No effect, you can still work
offsite or did you mean RDC?

How does it work? *** Back end on Server, front end on your workstation...
You need detailed, here's the link...
http://www.members.shaw.ca/AlbertKallal/Articles/split/

How will it update the data? ***The same way it always does. The back-end
and the front-end are connected and they talk to each other. They are just
not in the same house. Think of it like calling your neighbor... you can
talk to them and exchange all kinds of information without being in the same
house. More? Refer them to the above link...

Etc.

Is there any place that I can read up on this subject?

Thank you in advance.

 

[Jeff Boyce]

In addition to Gina's response, I'm curious why?

Why do your users care where the data is? If your application gives them a
way to get their jobs done, what does it matter where the data lives?

--

Regards

Jeff Boyce
Microsoft Access MVP

Disclaimer: This author may have received products and services mentioned in
this post. Mention and/or description of a product or service herein does
not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

 

[forest8]

Hi Jeff

While not savvy, there will be questions. I feel that it's better to be
prepared for possible questions than not to have answers at the ready.

 

[pietlinden]

How about

"Raise your hand if you would like the database to get corrupted
because you are all trying to access the same unsplit database at
once?"

I figure that if they know the risks they are taking by sharing an
unsplit database, they will come around very quickly. Besides, what
do they do if they want to create temporary objects or their own
queries?

The potential benefits of using an unsplit database just are not worth
the risks. Wait until your first database folds up on you.