Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / General 2 / January 2008

Tip: Looking for answers? Try searching our database.

Make a table

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Arunoday - 29 Jan 2008 07:20 GMT
Sir i want to design a table where i need to store the data of individual
with their clothing details.
Suppose a employee is issued 50 types of different clothes after specific
durabiility of that particular clothes. like if i issue a overall to a
employee, the table should contain the details with these fields:-
EmpID
ItemNo
ItemDescription
QtyIssued
dateIssued
ItemLIfe
NextDueDate
Here no fields are the unique fields because the same item can be issued
several times to particular individual..
now the point is if i want to issue 50 different clothes with the same fields
(ItemNo, ItemDescription, QtyIssued, DateIssued, ItemLIfe, NextDueDate) in
res[pect of the single individual the total field no. will be 250, and it is
really a heavy for for designed form to enter a data.

so sir, can u suggest me the easiest way to make a table with few fields.
here i need to store as well as retrieve the data from the table for future
use. where i can issue particular item after the expiry date of particular
item showed in the NextDueDate field..
Pat Hartman - 29 Jan 2008 15:11 GMT
Create a table where you will store the employee information, another to
hold information on the clothing items, and the third table is a relation
table to associate clothing with an individual.
tblEmployee:
EmployeeID
FirstName
LastName
...
tblItem:
ItemID
ItemDescription
ItemLife
....
tblEmployeeItems:
EmployeeItemsID
EmployeeID (foreign key to tblEmployee)
ItemID (foreign key to tblItem)
DateIssued
QtyIssued
NextDueDate
....

With this structure you have 1 row for each employee in tblEmployee, you
have 1 row for each item in tblItem, and you have many rows in
tblEmployeeItems that make the list of items assigned to a specific
individual.

> Sir i want to design a table where i need to store the data of individual
> with their clothing details.
[quoted text clipped - 22 lines]
> use. where i can issue particular item after the expiry date of particular
> item showed in the NextDueDate field..
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.