Database

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

Guest

Hello,

I would like to create a simple database that will allow me to track a
computer's maintenance service by a technician, or how often this computer
had to be serviced. How would I go about starting this task. I am new to the
database.

Thanks,

Alex
 
[email protected] said:
Hello,

I would like to create a simple database that will allow me to track a
computer's maintenance service by a technician, or how often this computer
had to be serviced. How would I go about starting this task. I am new to the
database.

Thanks,

Alex
Click to expand...
 
Hi Jessica:
I just started working with Access myself and attended beginners through
advanced training and I believe you should seek some form of training -
unless of course you have experience with some other database program - and
it is not at all like Excel.

But,to start a simple database you make tables that can be related to each
other. Like for instance a table with your technicians that includes all the
info you need on them like name, dept name, location etc, the next table
would have alist of remedy tickets that the technicians have worked on. You
don't need to type the name of the tech that worked on the ticket, instead
you get that from the first table by making the field for the tech a lookup
field to the technicians table and specifically the technician field, etc and
so on. Some tables might be real short like for instance if you have three
locations throughout the US you might list those locations on one table. that
table would only have three rows of information, but again you link into this
table by creating a lookup to the table and the user can choose the location
for that ticket or technician.

Map out your table on paper, then go create them. Don't forget to apply
masks right away, putting them in later wastes time. A mask will force the
user to, for example, type 10 digits for a US phone number and they don't
have to type parenthesis around the area code or put the dashes in, just the
number.

Then you build your forms to make it easy for the user to input data. If
you're going to be the only one to use the database you might choose to skip
making a form, the form utimately guides the user to put info into the tables
that you created. You can do that right in the table itself.

To retrieve data in an organized format for printing or viewing you create
reports. Reports use queries to look up the info in the manner you want.
Create a simple report with the report wizard, then add custom queries using
the expression builder. you can also start a report from scrtach without the
wizard, the wizard works pretty well though. Adjust the format and layout as
you build. the report is static. If the info in the tables has changed you'll
have to run the report again to see the new info.

I have not yet served my databse to users so I can't elaborate on ho that
works, I'm still in the learning phase myself. Good luck
 
recommend to both of you that you do NOT use Lookup fields in any table in
any database. for more information, see
http://www.mvps.org/access/lookupfields.htm.

also recommend that you don't use tables for data entry. FORMS are the
proper tools for entering/editing/reviewing data, whether the database is
single- or multi-user.

for some basic Access tips that apply to any database you may build, see
http://home.att.net/~california.db/tips.html. this webpage also includes
links to several excellent websites that i recommend you visit and bookmark
for future reference.

hth
 
Thanks Tina. I beleive you saved a lot of my time by taking a minute to
respond. I would have found that out the hard way. Thanks for the links.
Hmm...I feel much more comfortable when I can see the whole table and enter
the info that way, but I'll take you advice and use the form whenever I enter.
 
you're welcome :)

if Datasheet view is your preference, then just set the form's DefaultView
to Datasheet. you'll have the same "look" as a table's Datasheet view, but
far, far more control over the data entry process. one note to remember: if
you're opening a form using VBA code or a macro, you have to specify
Datasheet view, or you'll get SingleForm by default even though the form's
property is set to Datasheet view.

hth
 
Back
Top