Should i learn Access?

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

Guest

Hello everyone,

Here's my situation: I know very little about databases but need to create
one for my company. It would be a relatively simple DB, where employees
access it at different times and enter data, but i don't want them to be able
to modify another employee's data. For example

1 - 203943 Jeremy
2 - 283948 Frank
3 - 201029 Sarah

etc, etc.

I want each employee to be able to access the DB and enter info next to a
number, but not be able to modfiy any of the other's data. Also, i want the
whole spreadsheet to be visible to all. I imagine this has something to do
with permissions and assigning them, etc.

Does Access give me the options to do this, or should i learn another
database utility? I don't want to learn it if it isn't going to give me
these options.

Thanks very much in advance for any help you may be able to give.

Jason
 
Jason,

Contact me at my email address below if you would like outside help to build
your database. I can make you a hero by having the database you need up and
running in a short time at a reasonable fee.
 
Jason,

Access is probably one of the simplest applications to learn when it comes
to databases and programming. Simplest here does not neccesarrily mean
limited either. it is very possible to create complex databases and
applications.

As far as security issues are concrened there is a plethora of features that
will allow you to control who and under what circumstances a user can modify
data, there are built in wizards that can also guide you through the process.
My suggestion is go for it.
 
Jason

Based on the limited list of requirements you stated, Access should be able
to do this.

You need to know that Access has a fairly steep learning curve. If you have
limited experience/knowledge about relational database design,
user-interface design, programming, ..., you can expect to spend some
serious time coming up to speed.

Another issue to consider if you haven't designed systems before is that
"simple ... is HARD!" Creating a user interface that is simple to
understand, intuitive, and relatively bullet-proof is a whole different
matter from building a database.

If this hasn't scared you off from Access, and if you have some serious time
to devote, got get 'em, Tiger!

Good luck!

Jeff Boyce
<Access MVP>
 
Back
Top