JP-
The hard part is designing the tables for your application. From your brief
description, I see the following "subjects" and "actions":
Persons making requests
Items to be requested
Request and receipt
So, you need one table to hold information about Persons. Another table
needs to hold all the relevant information about Items. Each table should
have a Primary Key field that uniquely identifies each row - for simplicity,
you can use an AutoNumber field.
Finally, you need a table to record the requests and receipt:
PersonID - Primary Key of the person making the request
ItemID - Primary Key of the Item
DateRequested
Quantity
DateReceived
If a person can request an item only once, then the Primary Key of this
"Requests" table can be the first two fields. If a person can make multiple
requests over time, then also include the DateRequested in the Primary Key.
Hope that gets you started.
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
http://www.viescas.com/
(Paris, France)
-----Original Message-----
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of mccainjimmie
Sent: Monday, August 19, 2013 1:37 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] newbie help
I'm trying to design a database that keeps a record of requests items. The
person that requested and when they received the items. I have taken a basic
course but still having problems could someone help? Thank you JP
------------------------------------
Yahoo! Groups Links
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (3) |
Tidak ada komentar:
Posting Komentar