I would appreciate some help redesigning a database structure.
Currently the database has a table holding students personal details. Linked to this table with a one-to-many link is a table holding subject reports.
Also linked to the student table are two other tables holding prior attainment and mentoring details. These table are linked one-to-one.
Personally I believe the two tables linked with one-to-one links should be merged with the students table to become one single table holding student data.
I want to create a database with data stored in a directory/geneology kind of structure. I was thinking in a solution like this:
Table A (and sample data): Field ID_Person ( 1 , 2 , 3 , 4 , 5 ) Field Person (mary , jane , carl , bob , carmen)
Table B (and sample data): Field Parent ( 1 , 1 , 1 , 4 ) Field Children ( 2 , 3 , 4 , 5 )
Table C (and sample data): Field Car (1) Field Licence Plate (12-34-AB) Field Owner (3)
This tables let me know everything I want. I know mary is the mother of jane, carl, and bob. And that bob is the father of carmen. So, for each person I can easly see their children, and parents (if instead of relating ID_Person with Parent, I relate ID_Person with Children)
I'm using access and when I create the relationship ID_Person to Parent, I go to table A and by pressing the "plus button" all is fine:
Table A - 1 mary 2 3 4 + 2 jane + 3 carl + 4 bob + 5 carmen
However, I want to see the names of the children of mary, and also their own children if any, like this:
Table A - 1 mary + 2 jane + 3 carl - 4 bob + 5 carmen + 2 jane + 3 carl + 4 bob + 5 carmen
But when I add the relationship ID_Person to children it stops working.
If I add to table A the field "ID_Person2" with the same values of "ID_Person" and then create the relationships: "ID_Person to parent" and "ID person2 to children (now primary key)", I get the above structure as I itended.
But having two fields with the same value is very very ugly, so I would like to avoid that, but dont know how. Furthermore, I can't make children primary because a children has two parents, therefore, colum children will hold duplicate values).
Thanks Beforehand, Pedro Vaz
(if it changes anything, please assume a children may have any number of parents. I want to adapt this structure to other contexts without parents=2 restriction)
I have a database to record documents received on a project. 2 main tables, documents and revisions, each document can have many revisions. I have now been asked to add a section in for actions against each revisions, that is each revision can have many actions. Am having problems understanding how to add this table. The current database has several hundred records already and I do not really want to re-enter. Can someone help. TableDocument: counter(primarykey,autonumber), DocNumber, DocTitle TableRevision: counter, revision, DateRec'd
I am on my way to building my first relational DB. Is anyone able to look at the attached sample and tell me if I am on the right track?
The DB is being desined to record Repair information carried out on a machine. (TblRepair)
The DB will also eventually record refurbished machines (TblRefurb) and also many other situations like stock control, etc.(yet to be designed). Before I go on I just want to check:
> Is this roughly correct so far? > If I create a new record in the existing form, why can I not enter both UnitID and EmployeeID? Relationship conflict? > Should I be building forms on a query? (I think the answer is Yes, just need confirmation). > Is it because of a problem with the query I cannot enter details correctly? (as per the above question).
Any pointers would be very welcome. PS Sorry its v.old A97!
I have created a database with auto-archiving features. I have "working tables" that are populated when the product is moved to the correct process, in this case when it reaches the test department. When the product is moved out of the relevant process, the database runs several queries which archive the relevant data and deletes the records from the working table.
There are two working tables in the test department, one for test failures and one for rework activities. The question at hand is WHEN should I populate the working table for rework activities:
Option 1: Populate the table when the product moves to the relevant process. This will create and delete thousands of records from the working table every day. Using this method will cause my table to bloat to 50,000+ records that are constantly updated, appended, and deleted.
Option 2: Populate the table when (and IF) the product fails a test. This will keep the table to a much smaller size (around 2500 records) but requires the database to run several queries in the middle of the data entry process, significantly slowing my program.
So which is the faster/better process: Filtering a table of 50,000+ records or appending the working table when you need the data?
Is there any way to keep track of a database structure in access? For instance, which query relates to which report? Sometimes I create queries that are no longer needed but if there are a lot (which there are!) it can be easy to delete one that's needed.
I created a database to track tardies and absences of my employees. I would like to be able to sum the number of absences and tardies for each person per month and graph it.
Per our attendance policy, 6 tardies = 1 absence. I need to take the total number of tardies that month/6 and add to the total absences that month to equal the total attendance for the month.
I need help. Can you please view my database and give me some ideas?
I'm trying to find a way to export the structure of a table in my Access database.
I created a new table and I want to put it in the database on my website. However, my site is constantly being used so I have no way of downloading the database, modifying it, and then uploading it again without losing some data.
I do have a database editor on my website that allows me to run queries. So If I can get a query with all of the CREATE TABLE information (all the fields, whether they are Allow Zero Length, etc.) then I can just use that.
I can't seem to find a way in Access 2000 to export the structure of the table.
An engineer requests that “x” amount of computers are ordered for the company. The estimated costs of the system(s) are determined. The estimated cost of the systems is forwarded to a manager, and the request must be approved by a manager before the order is placed. Once the manager approves the request, the order is placed through the ordering company. After the ordering company approves the order, an order number is assigned and serial number(s) specific to each computer is associated with that order number. At this point it is possible to track the order status via existing programs using the assigned order number and serial numbers. After it is determined through the existing software that the order has been shipped, invoiced, and received by the Receiving department, I need to physically go pick up the systems and submit them into my Central Inventory. From the central inventory, systems will be checked out to employees as needed, checked back in when testing is finished, or transferred internally between employees......
Please, I really need some help with my normalised tables and relations:
1.AdmissionID AdminYr .......
2.StudID SName AdminID .........
3. ParentContactID Fname StudID
4. CycleNO cycname .....
5. DisciplineID Discname CycleNo StudID .......
6.SubjectID subName DiscID ....
7. ExamID examdate StudID
8. Results StudID ExamID mark ......
I have a feeling this relationship, is still a bit messy?
I also need to keep track of students daily class attendance, at the end of the tern, or year to find out how many students dropt out of a particular class etc. Is this a new table?
I have been reading up on normalizing table structures. I have this database that I am working on, to work as a hiring database. It should hold information about people applying to the law firm I work at.
I am looking for advice on if this table structure is normalized and sound. I am also looking for specific help on creating good forms.
Thanks for any help that can be given!
ps. I am attaching a zip that has a jpg view of the tables and their relationships, as well as the db with the table structure.
I would love any and all advice. I want a very clear concept for this db before I do anything!
Consider i have an employee database. And i want to keep a track and analyze all the training programs every employee has attended from the day he joined ( for both working and resigned employees). The analysis part is based on division-wise, level-wise, year-wise, location-wise, trainingtype -wise etc..
I have a main employee database with his ID, name, location, age. And i have created seperate tables for his designation, dept, training program, year ,etc...THe reason for this is that the departments, designation , training programs available within the company get updated often. And I have created relationships between them.
When an employee resigns or leaves the company, i have to store the records, but I dont need to update it. One option is ; whenever a employee leaves the company delete his related record and transfer them to to another table called OUT_Emp. Just the delete the employee record from the Employee table. And keep the other relationships intact.
Or should i create seperate database and transfer all the tables from the main database, just for the employees who have retired, resigned or suspended. THis database will contain all the tables that the main table has along with the relationship.
I am designing an application that tracks information on Choir membership and sheet music that we have on file. I am starting with a database of church members. There are four different choirs and choirs share some members. Some members of some of the choirs are also not members of our church so I will have to place non members in the member table. I am new to database design and would like the collective wisdom of this list to tell me of any problems I may encounter before I start doing any detail work.
What is the best way to deal with someone who is a member of more than one choir and may belong to a different section in this other choir (Tenor in one and Bass in another). An individual may also hold different offices in various choirs.
The table structure I have is as follows
CHURCH MEMBERSHIP DB: MemberId Autonumber (pk) FirstName, Text MiddleName, Text LastName, Text DateJoined, Date Phone, Text Address, Text City , Text Zip, Text EmailAddress BirthDate, Date Member, Boolean
CHOIR MEMBERSHIP DB (How do I efficiently track someone in > 1 choirs) MemberId, FK ChoirId, FK FolderNo RobeNo Section ChoirOfficeId, Fk
CHOIRS DB (This lists the various choirs in the Church) ChoirId, pk ChoirName, Text DirectorId, FK (Pointing to Member DB, Person may not be member of any Choir)
MUSIC DB CatalogId, PK Title Composer Arranger Type (Single Copy/octavo or book/collection) PublisherId, FK PublisherNumber VoicingId, FK (From table with possible voicing) NumCopies UsageId, FK (Where in the service is it appropriate Location, Text (Where in the filing system, or off site) ClassificationId, FK (List of classification/genre in table so can update)
PUBLISHER DB PublisherId, PK PublisherName PublisherAddress PublisherPhone PublisherWeb PublisherContact
MUSIC CLASSIFICATION DB ClassificationId, PK Classification, Text (Christmas, Easter, general anthem etc)
To be able to track performances and plan services and performances I have the following table.
PERFORMANCE DB (This is to keep track of and plan the regular service) PerformanceId, PK Pdate, date (Date of Past/Planned performance. Possibly more than one per day) ServiceTypeId, FK (From table of types of performances – morning service, evening, etc) Location Speaker Pianist Organist Introit Invocation Anthem Meditation Benediction (etc)
I would also like to be able to prepare mailing labels for the various choirs as well as the general membership from this DB. My primary focus will be on the music. I would like to have an efficient music DB that I may find out what music I do have and when I last performed them, what options for performance (usage and classification)
I don’t understand how to structure tables and relationships.
I want to build a form that allows the user to search for a postal service from a group of carriers.
User must be able to input into a form:
Weight in g, Kg or lbs Insurance level required Whether signature is required (Yes/No from drop down list) Collection/drop-off options (tick boxes)
Each service has a different insurance level, some need signature; some services collect, and all have different rates.
I just want to know how to structure the database.
The main part of my question is what would be my main table be and what fields would be contained in it, and what foreign keys would be introduced to pull in info.
Would you have a different table for each service?
I was having a discussion with a friend of mine about this... and I couldn't come up with the best explination. Hopefuly someone here can point me in the right direction.
I don't believe that this is the proper way to create a table. What happens if you happen to come across a Recipie that needs 6 items?? or more?? After researching it, I believe it violates 2NF. Is this correct?
I’m struggling to fix a database for my state agency. Here’s what the social workers need:
The agency holds several Foster Parent training sessions a year. Each session consists of 9 classes. We need to track ‘student’ attendance at each class. We also need to track class dates for each student.
The fly-in-the-ointment: ‘Student’ foster parents must attend the 9 classes, but they can fulfill this requirement over several sessions. They can take classes 1, 2 and 5 in Session 1, classes 3, 4, 7 in Session 2, and so on.
Here’s what I’ve created:
tblSessions SessionID SessionLocationkey ( to tblLocations; irrelevant to this post) SessionStartDate SessionName
The Attendance table is the junction table for the many-to-many relationship between Students and Classes.
Is this the correct structure? Thanks in advance for any advice. And thanks to Pat Hartman, The Doc Man, and SJ McAbney for getting me this far with the advice I found in researching this topic.
one customer can have more than 1 apartments, and one apartment can be transfered to another customer (file# same but customerID changed) one customer is paying different types of payments against his apartment.
please help me to manage tables and relationships.
I need to merge two Access DBs but I need to know if it is even possible before I start learning how to do it. It is not easy for me to express the problem but here goes:
DB A: -Flat Table with numbered indexes -will use a unique field as my index for the merge (not the primary key)
DB B: -The destination -One to Many relation (table 1 to table 2) -primary key not numbered field (I think) -will match primary key to the unique field in DB A -a few fields from DB A will be appended to table 2
....................DB B Table1----------------Table2 ******---------------************ *-----*-one to many-*-------------* ******---------------*-------------* -----------------------*-------------*----append----------DB A -----------------------************...<<<<<<<......*********** --------------------------------------------------------*-----------* --------------------------------------------------------***********
I need some help trying to setup tables on a new database. I want to setup a house analysis database where I can evaluate each room for it’s condition broken down by feature. I can’t seem to figure out a good way to tie all the rooms and evaluations back to that house’s address (primary key). I want the fields to work as shown below with the room evaluations tracked to each room and house address. If possible I would like to be able to enter the as many room names as needed for each address.
Company Company ID Program A Program B Program C Program D 2000 2001 2002 2003 2004 2005 The years indicate the year the Program participated in the company. For example, Program A participated in Company Z from 2000 to 2005, Program D participanted in Company Z from 2001 to 2002.
Should I have a table with the Companies and Program A and the years from 2000 to 2005 and a table for the Companies and Program B and the years, etc? I was going to add a yes/no field for each program, too. There must be a simplier way.
I want to be able to query participation of workers in any of the programs.
It's been a LONG time since I've designed a database, but it's slowly coming back to me. However, I'm still having a very difficult time deciding the most effective way to setup my tables and queries. Here's what's going on.
The database will be used for FFA livestock shows to enter the exhibitors for market classes and showmanship classes. The database also needs to be able to break a pay scale down showing how much each exhibitor is awarded for their showmanship class and their market class. The database that the club had been using had 2 tables (1 for the exhibitor and 1 for the animals being shown). Then they had 10 different queries that sorted the animals into weight groups (ex. Class 1 is weight between 90lbs and 100lbs); and then they had 10 different queries to breakdown the showmanship classes (ex. Showmanship Class is is age between 5 and 7). This is a LOT of queries! Now, the manager wants to be able to have more than 10 classes, which their current database cannot do. He also likes to be able to enter the parameters to manually break the classes. As of now, he is manually going into each query and editing the criteria for each class, but he wants to be able to do that from a form.
So my question is.... is it best to leave this in the "multi-query" form, or is there some way I could arrange all of this from tables or from a couple queries... and also, what would be the best way to offer the option to add a new class?
Hi, Thanks for taking time out reading my thread! I want to start entering data, but i'm not to sure weather my relationship structure is good enough to start inputing.
Heres a pic of my relationships http://img201.imageshack.us/my.php?image=almostdoneae0.jpg
i have been asked to design an access databse for a friend who is a bricklayer. He wants to use it to store all the work he does so he can produce his timesheet quicker.
He works on building sites and has to show a plot number next to all the work he does. He wants to be able to search for a plot number and see what jobs he has already booked in for a particular plot number.
For example, if he is working on a block of flats, each flat will have individual plot numbers. If he is working on the outer wall of the flat his timesheet has to show all plot numbers for that block so he will normally show this as plots 100-110. however, if he works on an internal wall in one of the flats he will have to show just one plot number on his time sheet, for instance plot 104.
my problem is that he wants to be able to search for plot 104 and have it list both jobs he has done even though one job is shown as plots 100-110. How can i structure the database tables to allow this to happen.
hi everyone,i'm new to access and despite reading quite abit im just not grasping how to set up tables and relationships for what im wanting to do.I need a customer contacts table/form to keep track of my customers info (name, address, etc) & who's placing orders, easy enough.Now with some of my customers its always the same person who places the order but with others it can be anyone of up to about 15 different people who place the order each one can have their own direct phone no.So what im wanting to do is create a customer contact table/form and then linked to that who in that company placed the order with their phone no. Ideally i'd like it so once I have entered the info I can just use drop down menu's to select the company name then it opens up a list of all the people who I deal with in that company so I can just select the person/phone no who is placing the order.Can anyone help & advise me through best way of doing thisthanks alot
