Asset Tracking Database

[SouthernBoy]

I'm still new to Access and know enough about this program to make m
dangerous (or confused). I'm trying to set up a Computer Inventor
database for our elementary school.

The fields I need are

Asset Tag - number given by our Acct De
Service Tag - Serial or service tag on the p
PC Name - name of pc from our Network Administrato
Operating System - OS installe
Model - all are Dell's....model of p
Type - desktop or lapto
Date Verified - dat
Verified By - employee's nam

On the form, I was wanting combo boxes for OS, Model, Type, an
Verified By. Also, in the end I would like to create a switchboard t
where an employee can either "Add" a new pc (or record), "Modify o
Update" a current record, or "Delete" a record

Does anyone have any ideas of how I can start pursueing thi
adventure? Like I stated earlier, I'm familiar with the very basi
functions of creating tables, queries, forms, and switchboards. But
I do need direction on the actual design portion of the database an
how to link the combo boxes. Also, would Relationships play a bi
part in this database? Do I need queries to create the forms

Any help in this matter is much appreciated

 

[Dodo]

(e-mail address removed)-spam.invalid (SouthernBoy) wrote in

I'm still new to Access and know enough about this program to make me
dangerous (or confused). I'm trying to set up a Computer Inventory
database for our elementary school.

Would this be something to start from?

http://office.microsoft.com/en-us/templates/TC010184591033.aspx?
CategoryID=CT011366791033

Sorry, that one is a bit long and running off the screen so I hope tiny
helps here:

http://heh.pl/&I1

 

[SouthernBoy]

I had actually tried using this, but this one is a bit too in dept
for what I'm needing. I have been looking at this database to ge
ideas on how to approach the design portion for what we are needing
Thank you very much for your response

 

[tina]

would Relationships play a big

part in this database?

yes, as they do in virtually any database. defining your tables and
relationships is the FIRST and most crucial step in building a relational
database. it's not an easy topic for most people to grasp initially, and
takes reading, study and practice to become proficient at it. these
newsgroups are full of questions from folks who either didn't know about
this step, or didn't bother to take it, and are now paying (and paying, and
paying) for that mistake. i strongly urge you to learn the basics of
relational data modeling before you begin building your database. one good
resource is Database Design for Mere Mortals by Michael Hernandez. other
good resources may be found via the links at
http://home.bendbroadband.com/conradsystems/accessjunkie/resources.html
beginning with the Starting Out and Database Design 101 links.

once you've mastered the basics of relational design, a good text to help
you develop a functional "end-user" application is Microsoft Access
<version> Bible by Prague and Erwin. it gives step-by-step instructions on
creating basic db design elements, and gives you a good foundation to move
on to more advanced design techniques. also, suggest you explore the above
website; it offers lots of helpful design tips, and links to tons more
information.

hth

 

[SouthernBoy]

Without going into much detail, I have finally learned the proper wa
to design a relational database with combo boxes. My problem wa
creating/defining a foreign key so I could establish a "one-to-many
realationship. As I stated earlier, I am familiar with the basi
concepts (thankfully). But, for the person that has the similia
problem after we leave this topic and move on, I will have to sa
that relational databases can get very confusing at times and ca
really steer a person to quitting. BUT DON'T QUIT! These forums ar
compiled of information about all topics. Relationships DO play
huge part in databases and other points of interest are the "keys
(primary and foreign). My problem lied within combo boxes "lookin
up" data from another table. Setting up the "primary and foreig
keys" in the tables is essential before building "relationships".

I breifly looked at the links above since I had already solved m
problem before reading this post, but I will be using these in th
future as they looked to be very informational. Thanks to all tha
helped me through this situation. All posts were very helpful than
you for the info links

 

[SouthernBoy]

I'm still having a problem with data from a table showing up on m
main table in a combo box (or Lookup field).

Ex. On my Computer table I have a field called "StatusID". I'
wanting this to reference the "Status" table and return the value fo
the "Status" column.

Computer Table Field:
StatusID (number type

Status Table Fields:
StatusID (autonumber type and Primary Key
Status (value of status that I'm needing returned to the mai
table

My relationship for this is a "one-to-many" where "Include ALL record
from 'Computer' and only those records from 'Status' where the joine
fields are equal.

http://www.geocities.com/the_southern_boy2001/access.GI

Can someone please tell me what I'm doing wrong? I thought I had thi
figured out. You we could also maybe link up on MSN or Yahoo mess i
needed. I'm "the_southern_boy2001" on both. Thank you

 

[Duane Hookom]

Lookup fields are generally a bad idea. Check this out
http://www.mvps.org/access/lookupfields.htm.

If you want the Status text to appear in a form or report, you must either
use a combo box or add the status table in the record source. BTW: you
should be using a naming convention. Having fields and tables with the same
name is generally not a good idea.

 

[SouthernBoy]

Great response. You are definitely right about the naming conventio
and I had aready planned on a different scheme when I was trying t
explain my last post. Even I was getting confused (lol).

On the combo box, are you saying I should create the combo box on th
form instead of in a table (in the lookup section)? Once created o
the form, how do I get the combo box selection to show up in th
table? What I mean by this is everytime I have used sample data an
went back to open just the table, there is a 1, 2, or 3 in the field
I can see the combo box in the table and also see the selections ("I
Use", "Disposed", etc), but by having the tables "related" by th
StatusID field (autonumber in the Status table and number in th
Computer table) it won't let my select text for a valid entry

Note: the link above didn't work for me. This maybe on my end th

 

[Duane Hookom]

Open the sample Northwind database and see how they use combo boxes on
forms. Ignore their use of lookup fields.