database design

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

My database will be used by multiusers. What is the best approach to
designing the database?

Do I need to split the database and replicate it? I am still new to this
area. Please share the answer as specific as possible.

Thanks.
 
Dear AccessHelp:

Access databases are multi-user right out of the box. Splitting the database
is an essential part of creating a well-designed multiuser database
application. Replication is something different altogether, it has to do
with synchronizing data between on and offline copies of tables, and its
probably not something you want to get into.

When you "split" a database, you create two separate .mdb database files:
one file holds the tables of data, and the other file holds all the forms,
reports and queries and so on. The file holding the tables of data (often
called the "Back End"), is stored in a shared folder on the network server.
Copies of the file with the forms, etc., (often called the "Front End") are
stored on each workstation. The "Front End" .mdb database files are "linked"
to the Back End" .mdb database files, so that all users have access to the
same data. There is a database splitter tool available within Access to help
with the process.

There is good information here:

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

and here:

http://www.granite.ab.ca/access/splitapp/index.htm

Post back if you have further questions!

HTH

Fred Boer
 
Hi Fred,

Thanks for your help. I do have a few questions to ask.

I had done the way you mentioned in your message. I splitted the database
into two (BE and FE). Then I linked the tables in FE with BE. If I do that,
when a user is accessing Table A through Form A, the second user may not
access the Table A from any form at the same time. I think that may be the
problem? So basically, no two users can access the same table at the same
time.

What are the problems that can occur using the replication? I thought
replication is a good tool to use? If I replicate the whole database, I can
then send it to the users to use. The users can access any table and do
whatever they want. Then periodically, I syn them back to my Design Master.
Also if I happen to make changes to the form design or any addition, the syn
will reflect to the replicas. Am I correct? Am I missing something? Again,
I am still new to this area.

Thanks for your response and help.
 
Hello!

I assume you have the back end table in a shared folder on the server, yes?
All users must have complete privileges (permissions) on this folder. I
think that might solve the inability of two users to access the data file
simultaneously.

And each user has their own individual copy of the front end file on their
own computers, yes?

As far as replication goes, I have to say that I know little about it. The
situation you describe is, (I think!), what replication was designed to do.
I thought you were talking about setting up a multiuser application over a
network. That is what I was discussing; if you are talking about a multiuser
application with users working offline, well, that's a whole 'nuther kettle
of fish, and I'd be no help there. Perhaps someone more expert in
replication will step in here to help you out. If not, you might want to
post a separate thread about replication...

HTH
Fred
 
Dear AccessHelp:

I notice that you are discussing this same issue in another newsgroup
"microsoft.public.access.tablesdesign", under the heading "Multiple Users
Environment". Seems to me that you are getting the same information in two
different threads. Lynn and John are Access experts, far more knowledgeable
than me, so I think I'll bow out of this thread. No sense in duplicated
effort!

Cheers!
Fred
 
Back
Top