database configuration

  • Thread starter Thread starter cheryl
  • Start date Start date
C

cheryl

I am a newbie with databases. We have built a database
that only has the forms and tables done. What is the next
step. Do we need someone to develop architecture (how
many users, how the information is going to get to the
server?....) before this is rolled out to sites? What
would be the level or title of the professional needed to
do this?
 
Cheryl,
The answer to your questions depends entirely on the business requirements
for the database. In fact, there should have been a business requirements
document created before you ever started creating tables or forms. If you
haven't done that, or haven't had one given to you by the people needing the
database, then it's time to go back to square one.
 
Cheryl,

It sounds as if you have done much of the work. Do you
have all of your forms working so that the general user
will have no problems navigating through the data entry
processes?

I assume from your posting that you are going to be using
this database on a network. If so, there are many things
that would need to be considered. Numbers of users is not
as high a priority as the type of network and where users
are located in relation to each other, ie: lan or wan.

One thing of serious importance is: If you are going to
be in a multi-user environment, then you need to split
the database into a front-end (an mdb file or an mde
file) that will contain all of your forms, queries,
modules and reports and a back-end file (an mdb file)
that contains only the tables you are using for your
application. You did not say which version of Access you
are currently using, but you can use the "Database
Splitter" wizard to accomplish this. This modification
will provide a much more efficient and user friendly
enviroment for your users. I will cause fewer record
locks and other user interface issues.

When the database has been split, you can then put the
back-end file in a folder in a shared network location.
You will then need to change the link path in your front-
end file to link to the tables in the mdb file in the
shared network location.

You would then place a copy of the front-end file on each
users hard drive, create a shortcut for them to use on
their desktop. Each user would then be able to use the
application.

There are always other issues, but this is a start.

If you are looking for a consultant and are interested,
you can contact me directly via e-mail by taking out the
undersocres and everything between them in this email
address : mrbpolk@_TakeThisOutNoSpam_cox-internet.com

HTH

Byron
 
Cheryl,
There's no standard way to do a business requirements document. Basically,
it just needs to include what you are trying to do with the database. What
kind of data you need to store. What kind of reports you will need to
generate from that data. To put it simply, a database should exist to solve
some kind of business problem. If you can describe what the problem is that
you are trying to solve, then you will have a good start on a business
requirements document.
 
Back
Top