I am writing a access database for work(fire dept). It is a database for the vehicle checks. Most of the fields are Boolean fields we just need to know if the inventory is on the unit. I am kind of new to this. My tables so far are as follows:
all list the inventory that is supposed to be in that table
Everything is dependant on the Vehicle it is on so my question is Do I relate everything to a look up field in TUnitNumbers(intUnitNumberID) or is there a better way to do this? I need to relate everything to the date it was checked
Hi all. I really need help with this. Does anyone see a problem with my relationships , i have attached a copy. Any help will be greatly appreciated ClaireB
I am new to database design and curious about relationships. In a hypothetical situation, if I have four tables: tblProducts, tblOrders, tblEmployees, and tblCustomers, how could the relationship be set up?
The Products are stored to keep track of the quantity on hand and the employees will also need to be tracked as to how many products they sell. Customers are recorded and Orders wrap up all three tables with the fields: OrderID, ProductID, EmployeeID, and CustomerID.
Would it make sense to say that many products can be bought by many customers and/or many employees can place many orders.
I've selected a number of tables to the relationship window. When I drag the primary key on one table to the corresponding foreign key on another table, the link created is one-to-one. I want one-to-many. Why did it create one-to-one? How do I change this to one-to-many?
Hi all. I am new to the use of access and have been told that I need to create a one-to-many relationship to be able to have several records from a drop down list saved to one unique number (my primary key).
Is this correct and if so how do I do this? If it is not correct what is the best way to do what I require?
I have created two tables which are linked with a one-to-many relationship
Using a form the user enters a date. Then in VB I add a value to the date and store this in the second table.
I have simplified this to try to find out what was going wrong and found that when the database adds a value to the second table which only has two fields it first of all adds it to the begining of the record set and the id field does not update to that of the first table where the relationship is joined.
Do I just captutre the value of the id field and add this to the recordset. How to I get the database to look foir the end of record set before I appent the new generated record.
I have looked for this on the help section; however, it does not seem to be covered. How would you change a one-to-many relationship to one-to-one? Access seems to automatically guess that the many side is where the foreign key.
Can it be changed from Access or is entirely on how you design your tables?
Hi !! I am doing a school project on a school database. In my DB I have a table with all students records (eg. Student ID, Name, Surname, DOB, class etc) and I have another table where the student fees payment slips will be printed. The fee table will only have the ID, name, surname and class fields and fee will be input for every student for every term.
I want the fee table to get all the info except the fee from the first table automatically when I give a student ID.
I have created a one to many with only Student ID fields linked, NOTHING.
Then I tried to link many fields on each side (eg Name to Name, Surname to Surname etc) but I got a msg "No unique index found for the referenced field in the primary table"
would having a db with several tables and NOT setting any relationships up in the relationships window affect the db in any way?
i have such a db, which originally had all the relationships set etc. however, as i encountered errors and had to replace tables and delete entries, i must have at some point deleted all the relationships.
i just relaised that the db now has no relatioships set up (all the primary keys are still in the tables) so i'm wondering if this matters?
If I have a table "tblContinents" with just two fields ContinentID and Continent and I have another table called "tblCountries" with three fields CountryID, Country and Continent.
After reading several articles, i decided not to make the Continent field in the tblCountries as a lookup field but rather I will do that at form level via a combo box. In such situation, since i am not creating a lookup field at table level, do you think that it is necessary to create the relationship between the two tables in the "relationship window", or shall i just leave it as it is, and if the need arises i will create such "relationships" in queries?
hi, im new here and i dont really know much about databases with access. im currently doing an assignment at school requiring me to do a entity relationship diagram for all my tables, which i do not know how to do. Can anyone please assist me asap? thank you very much in advance
below is the link where i uploaded it because it was too big to be uploaded onto this post. :)
I want the one-to-many relationship to be based on my own generated quote reference rather than the PK/FK.
My quote reference looks something like this IN123/10
Does the character '/' cause a problem with creating the relationship as I get the error message "No unique index found" even though I know that they exist?
When I view the relationships window, not one of the relationship connector lines (whatever the technical term is) do not show up! I click view all relationships, view direct relationships. I restarted my computer, restarted Access. Nothing!
I know I have relationships because when I am table design view I try to change something that I know has a relationship and it doesn't let me because it says I have a relationship.
Here is what I have. The database is made up of three tables (see below and see attachment). I have it set as one event to many ethnicity's and many personnel with the event ID as the PK in all three. Did I do this correctly? I thought I did and I had a form with each one of these running correclty but now it is not working.
tblEvent EventID(PK)
tbleventEthnicity EventID (FK)
tblPersonnel EventID(FK)
See attachment for the other fields.
Can someone just check to see if I set this up correctly or what I should do differently?
I have already made a relationship 1 to many, i want to add another relationship. I put the name of the feilds i want to join up in the drop down box. I put "enforce in..." and "Casgade update related fields" on and join type 2. Then when i press ok, it comes up with "file title " to "film title" and comes up with "no unique index found with the referenced field of the primarytable".
OK. I'm not real sure how close I am on this. I have a feeling I'm not too close so I was hoping I could get some help. I have a database with 11 tables. These can be seen in the screen capture attached. For the 'Action Taken' table there are 10 fields for 'Departments Involved', 15 fields for 'Memo Sent To', and 15 fields for 'Job Title'. The 'Departments' table is linked to 'Departments Involved1', the 'Memo Sent To' table is linked to 'Memo Sent To1', and the 'Job Title' table is linked to 'Job Title1'. All the other tables are showing the fields that are in that table. When I enter a record and try to go to a new record it gives me the following error message.
"You cannot add or change a record because a related record is required in table "Background Information'."
I'm not sure what to do about this. I'm sure there is a simple solution but I don't know what it is. I am pretty new to Access (this is my third week on the job) and a little confused on some things. I would appreciate any help you could provide.
Hello. I'm new to databases and anything I know I've read up on. I know that relationships are essential so I'm trying to sort a database in ms access that I have inherited at work. It contains health service staff and their record of training - various training that they do regularly. I've managed to put the data in 1nf but am having difficulty after that.
A couple of questions:
If I give each staff member a unique id do I need to link their job title to it? Job titles chang quite a lot.
Other information about courses, dates of training, trainers etc. - should they be linked to staff name via separate tables?
I'm using a spreadsheet example from microsoft that shows me how to go from raw data to 3nf but I'm not sure how to split the information, so if you have any suggestions or know any good guides I'd be grateful for your help.
i have made a form to enter the data, all works ok. I built a form to search by customer and it works fine. I can not find a way to build a form to search by boat name or serial. Can some one please help?
I think that's ok but it's when I try to link them I get into trouble. Assuming the above is correct do I have: TBSTAFF linked by STAFF_ID to TBCOURSE-COURSE_ID TBSTAFF linked by STAFF_ID to TBTRAINING_DONE-COURSE_ID
I'm not sure how base and dep/ward work either. I need to know a person's base and dept e.g. hospital x, ward y.
I'm trying to create a db to store for example Company Details, Staff Details, and Address Details. Each company may have multiple addresses Each staff may have multiple addresses Each Address is EITHER a company/staff address The address table structure is the same for both Company & Staff
I have come up with three solutions, each of which does not seem correct.
1) Create two Address tables each linked one to many from the Company/Staff PRB: Duplicate address tables seem inefficient and queries/future modifications will need to be duplicated
2) "Tag" the address table either by adding an additional field specifying if Company/Staff, or programatically manipulate the key (+ve = company; -ve=staff) PRB: Lose referential integrity: extar manipulation of queries, code etc.
3) Create a Junction Table with fields for the Address Key, Company Key, and Staff Key. PRB: Not really a many-to-many (as Each Address relates to one of Company/Staff); Not normalised as either the Company or Staff Key will be empty
I'm sure I must be missing the obvious, but any suggestions would be greatly appreciated.
:eek: I am having some trouble with parent/child relationships in my tables. I know what I need them to do, I just can't get it done. Please help! see attachment:
I need my tblDescription to be the parent. I need tblchecks to branch from tblDescription. I need tbllocation to branch from tblchecks to make everything jive in my world.
ok the last few days ive been putting together a database to make my business run a bit smoother but ive hit a wall and need some help. what im trying to do is have the 2,000 or so items i sell to differant industries put into differant categories so i can print a price list according to what they usually buy from me. now this part ive got done, what i need to do next is make it so when it prints the 500 or so items associated to this company it automatically splits the items into sub categories on my reports page. now i have a basic idea of what im spose to do but just dunno how to do it so heres the SS of what i got so far and what i think i need to do. any help on this would be great or point me in the direction of a tutorial that could help me.
ok so here i have my items list and as you see the drop down box on the left shows me what category this item belongs to, what i need to do now is make it so the item type has this same thing and shows me what item type it is, either by number or name doesnt matter.
now heres my relationships, the item ID and cat ID of the middle table were primary keys but with my messing around i kinda removed them but that i can fix later. what i need to know is do i need to connect my items types table to the tblCategoryItems via ItemTypeID. also i think i need to populate tblCategoryItems with the info from tblItemTypes via a query of some sort like i did at the start when making tblCategoryItems. if i do i dunno how, i only know how to make get this far i dunno how to add a 3rd table to this.
ok this final pic is what i need my reports to look like with the item types split into differant sections with a small heading of what it is, this part i have no idea how to do but if i can manage to get the first tables setup thn i can move onto figuring out this problem.
I need help with my relationships and form structures. Attached is a sample database for illustrative purposes.
Here are the rules I am trying to follow:
One client can have many banks. One client can have many bank accounts. One bank can have many bank representatives. One bank representative can work for only one bank. One client can have many bank representatives.
Are my relationships correct?
I need a form/subform structure where I can select a client and then select their bank(s) and input their bank account number(s). Then I need to be able to select their bank representative(s) - - this list should contain only bank representatives related to the currently selected bank.
A working form/subform example would be excellent, if at all possible.
I have worked with this for a few frustrating days.....I'm not sure if I am approaching it completely wrong or missing something small.
I have been battling this for awhile and this is a result from the thread below: http://www.access-programmers.co.uk/forums/showthread.php?t=97048
However, it seems more fitting to have the thread continue here as I am moving onto the relationships.
After setting up my tables and attempting to have Normalization - I am now faced with the Relationships of the tables. Can someone please look at the attached picture showing the relationships that I set up and let me know if I am way off or right on the money.
