I have built tables in MS Access for a very simple shopping cart.
It includes:
Catergories, Item, Customer, Shipment types, and Basket (cart). (for site)
There is also a User table, but that is only used for the Backened side for login.
This is what I want the User in the backened to do:
-add/edit/del Categories.
-add/edit/del Shipment type.
-add/edit/del Items according to Categories. (in one category, it can have many items, yet one item can go into more than one category).
This is what I want a browserer to do he/she enters the Site:
-he/she can add item(s)(which are under categories) to cart[basket](no login needed).
-At the basket(1 page), the user can view all the item(s) it chose, be able to change quantity, display subtotal, VAT, Shipment price, total price and enter it's customer details (e.g. name, mobile, etc), then sends form. These details are then "added" to the database and sends notification to admin(user) email. Therefore, no payment via client/server.
My problem is the relationships in Access.
Do I need to connect all tables? I tried connected my ItemID table to the BasketID table and it got a bit confusing from there.
Also the Categories got all messed up on me.
See my screenshots:
http://salis.aspfreeserver.com/sample/relationships.gif
http://salis.aspfreeserver.com/sample/table_menu.gif
I've got a problem with a make-table query that creates a new table which is then populated with new values that relate back to the original table the trouble is the make-table won't run with that relationship in place.
Is there a way to delete the relationship then reinstate it after the query? or any other way round that someone can think of.
We have customers, cars availible and the date and time and location etc... of when to pick up the customer
So 4 tables i have so far:
cars customers Bookings Drivers
a field in Bookings known as customerID is joint to the customers table, field CustomerID. a field in the Bookings known as DriverID is joint to the Drivers table, field DriverID a field in Bookings known as CarID is joint to the cars table, field CarID
I am wondering, does this sound ok to you? i am not great with relationships but i am improving. does this sound ok?
Another Q is, i need to know what times of bookings are availible. What is the best way of going about this?
How can I have table data refer to other data in the same table? For example: If I have a table of people I know, and I want to 'link' family members together, and these other family members are also listed in the table of people I know. Table: People Field#1: PersonID Field#2: PersonName Field#3: FamilyMember1 (using the PersonID) Field#4: FamilyMember2 (using the PersonID)
I hope I've explained myself clearly. Thanks for any help. -E
One with details of people's information (mothers).
We also need to enter information for their babies.
Basically I have set up a form with the info for the mother's details, and she has a Mother ID. The baby also has an ID which should be the same as the mothers (linking the two tables).
When I enter the info into the form for the mothers details, I hit the command button that opens the baby's details, however it has not created a baby ID that is the same as the mother's ID, therefore there is no relationship. If I enter in the baby id, and fill out the form - I goto the table and see that it has made the link and the information is complete. However, I don't want to have to enter the ID each time.....I just want the mother's ID to carry accross to the baby's ID field, hence linking the two.
I am having problems with a current database i have designed which was initally for Products/Stock. I now want to intergrate Services into the equation. I have attached a proposed design, but whenever i add the Services table and relationship, everything, in the sense of data disappears.
I'm having trouble modeling a relationship in a database. I need conceptual help. Here is an abstract description: A Class has several common attributes, but there are some attributes that differentiate different instances of this Class. For example, this Class may have x fields. ClassB will have those same fields and several others, so Class B will have (x+y) fields. Class C will also have x fields and an additonal Z fields for a total of (x+z) fields. x and y may be the same number or not, but they will certainly not be the same type of fields. See attached for picture.
My thinking is that since all the classes have x fields in common, why not have super class in its own table (ClassA), and have two (or more) tables composed of y and z fields respectively. The primary key (A1, lets say autonumbered) in the ClassA table would also be the primary key in ClassB and ClassC tables.
My goal is is have a subform within a form, where the form has all the fields from ClassA and the subform will have all the fields from either ClassB or ClassC depending on another field in ClassA (A2, text type for example). In essence, the layout of the subform would change depending on the value of A2 from the ClassA table.
Can this even be done. I think I'm missing something here. Would anyone care to offer advice?
I have no records in horse_information yet. I need it so that when a record is added to the first table then whatever is added to ent_HorseName is added to inf_HorseName. So I want all the records from horse_entries in horse_information. I want to be able to add to horse_information without that record being added to horse_entries. What kind of relationship should I use. Thanks
hi, im a a level it student and my current coursework is making a new program/system for access im making a new order form for the shop where i work and i want to link sundries on a diff order form to sundries on the main order form so it prints it all off on one sheet, basically i want to know how i can get the realtionship between ID number of the order, and the sundrie to link together, and if its possible at all, if its not ill have to change my project slightly which i dont mind, just wondered if any one could help me out a little thanks!:p
I'm just putting a database together, and I'm having a relationship "issue". It's fairly simple right now, but I'm not sure if you can do what I am trying to do..
Basically I have, so far, 3 tables. Each one has a primary key "Serial #".
There's a "Systems" table, a "Parts" table, and a "cash flow" table. I have a link from
Systems - Cash Flow Parts - Cash flow Both links are set to enforce referential integrity (with cascade update/delete enabled as well).
What I want it to do is work so that I can add new values to either the Systems or Parts table, with their own unique "Serial #" code, and then be able to add the value to the cash flow table.
Currently, I can add items to the "Systems" table, and then add the corrosponding entry into CashFlow, and that's fine. If I try and input an invalid entry, it will tell me that the appropriate entry does not exist in "Systems".
However, I cannot add anything to "Parts", since it gives the error that the appropriate entry does not exist in CashFlow. Obviously, I need to make it in Parts first, and even if I wanted to make it in CashFlow first, it wouldn't let me (entry does not exist in "Systems").
I have tried fiddling with the relationships, but I get other problems like not being able to add items to "Systems", etc. If I try and drag "Parts" to "CashFlow" the other way (in the relationship), it tells me that I cannot do that because it violates the integrity rules.
I can see WHAT the problem is, and I know WHY it's doing it, I just don't know how to fix it.
Basically, I want the field "Serial #" in the table "Cash Flow" to be able to draw from the field "Serial #" in either Parts or Systems, but reject anything else (in other words, incorrect serial numbers, since the item shouldn't be in the cash flow table until it has been registered as an item in either "Parts" or "Systems").
I am having a bit of troubles in my design conceptualization i believe. I am building a database to keep track of a companies liabilities....therefore i have several liabilities that all belong to one company. I have one table that is called 'client information' that lists the corporation name which i have identified as the primary key. My other table is called 'liabilites' and i also have a corporation field in that table but i can not define it as the primary key because i want to have several payments under one company.
I am looking for an easier way to confirm that all a queries that are in a database are being used by the database. I started going through each and every one and it is taking for ever!
I have tried the documenter and either I cannot understand it properly or it does not contain the information that I am looking for.
An example might be I have a query called qryOne. I want to see where it is being used so I am looking for a “list” that says
Obviously these are just made up names, but I hope you understand what I am looking for. In essence a relationship table for queries, forms and reports.
I was hoping to get pointed in the direction of some relationship theory. I am new at this and was wondering when, where and how to implement relationships into a DB. I am sure this has a lot of good uses, but I am failing to understand it completely. Any and all help is appreciated.
I have two tables, table 1 with client contact data and table 2 with client needs, both are auto numbered. I have two fields that are titled LastName & FirstName that appear in both tables. When I enter a new client in table 1 I want table 2 to automatically be updated with the clients first and last name. For example: If both tables have 4 records and I enter a new client in table 1 I want table 2 to be updated with the new client first and last name information,so both tables would now have 5 records. How do I create this relationship? Any help would be appreciated. If I haven't explained this well please let me know. Thanks. :confused:
I am working on this database where each category contains certain thickness ranges that can be stored in a pack of x amount and finally paneltypes. ie KS1000 only comes in 40mm 50mm 75mm and paneltype MR is the one associated with it.
there are 3 tables tbl_Customer tbl_catergory tbl_product -------------------- tbl_Customer: -CustomerID (autonumber) Primary key -CompName -CompAddr -ContactFName -ContactSName --------------------- tbl_category: -CategoryID (autonumber) Primary key -Category (combo box) this has set values entered i.e.
KS600 KS900 KS1000 KS1000LP KS1000RW ------------------ tbl_Product: -ProductID Primary key (autonumber) -fkeyCategoryID (foreign primary key) -Thickness (combo) this has set values of thickness ie. 40, 50, 55, 60, 70, 80, 100, 150, 180 -NoInPack (set number directly related to the Category and thickness chosen) i.e. Category KS1000 with thicknesses of 55 can be stored in a pack of 17. KS1000 with thickness of 60 can be stored in a pack of 22.
-PanelType: (combo box) set values as follows: MR (this selected item relates to products KS600 KS900 KS1000 ) EB (this selected item relates to product KS1000RW ) CX (this selected item relates to product KS1000 ) MM (this selected item relates to product KS1000 ) WV (this selected item relates to product KS1000 ) --------------- I would like to be able to setup a form that a user uses to provide a quote: It would start with using the Category combo box which lets you select one of the choices (i.e. KS1000) but the combo box would also have multiple column headings ie. Category/Thickness/NoInPack. Once selected then the next several individual field boxes (ie. thickness, NoInPack) are automaticallly populated with the selection just made in the Category combo box.
NOTE: Many categories can be chosen just for one record. I therefore do not want to start setting up fields like Product1 product 2 etc and their associated fields like thickness1, thickness2 etc. I'm failing in the relationships section. Please see attached database. I have tbl_category: CategoryID (1) --------> (many)fkeyCategoryID from tbl_Product I have tbl_Product: ProductID (1) -------->(many) CustomerID from tbl_customer I know that i need a junction table somewhere.... but i'm a newbie when it comes to this stuff. Any help would be appreciated.
I'm making a database of spare parts for machinery. But I came upon the following problem : A part can sometimes be used is more that 1 machinery. But I do not understand how I put the ID of all the machines in 1 field of that spare part
As I continue my pursuit of MS access knowledge, I am moving to table relationships and would love if someone could point me to a good source to explain in detail when, where and why to use table relationships as well as how to implement this. Thank you much!
I am very glad to have found this forum, as I really need some help. I work for a non-profit and was asked to develop a database that would allow our services people to input data on employers that have been visited and track followups. I've tried to sort of use the "Access 2003 Inside Out" book by Viescas and elements of his LawTrack contact database sample. Confusion reigns supreme at this point. I've done some topical Access work before, and have even set up some simple databases using InfoPath as a front-end, but nothing this complicated.
I have the tables, and have attempted in multitudes of ways to establish the proper relationships. The most common problem is when trying to enter information into a form, at the point where it's time to enter contact information (three associated tables), I get that funny bell sound, and it won't let me enter proper information. A couple of times I noticed after completing all other fields and proceeding to a blank record, then coming back to it, it will then let me enter info.
I've changed the relationships and keys multiple times to no avail...:confused:
Here is the graphic of the relationships: http://www.jcindustries.com/employerdatabaserelationships.png
I need for tblCompanyContacts, tblEmployerContact, and tblContactEvents to talk to each other and to tblEmployerDemographics as there are many contacts to one employer and you might have many contacts for one employer but only one can be primary.
I'm thinking the contacts-related tables would be best nested as a subform in a main form....when I try to generate a form on those three tables using table wizard, I get a blank form :confused: I know the whole problem is how to use the keys and their relationships, but I'm key stupid at this point :rolleyes:
I'm just at the start of database project to see if I can reproduce some kind of Management Game.
I'm quite focussed on making sure I have an efficient design for the database at this stage.
I've created most of my tables, and have also created most of the relationships between them, however I've got a couple of issues which I'm ummming and ahhhing about, to which I thought I'd see if anyone in here could help me.
1. I have a player table which will contain numerical values from 1-20 (Not integers) for different player attributes. The value of those attributes will be looked up and a text entry returned for any reports which would be seen by a user.
I want to do this for more than one type of attribute (i.e. Strength, Speed), is it more efficient to store all the text entries for those attributes together in one Attributes Table, or to store them separately in different tables?
(The text entries may be different for some of the attributes; this data would often be reported on collectively).
2. I have a Teams Table; each team would belong to a Region and then a Country with each Country having more than 1 Region. (i.e. ‘Yorkshire’ and ‘Lancashire’ would both be part of The UK…. All be it quite possibly not altogether happy about being next to one another ;-) )
Should I relate the Teams Table to a Region Table and then relate that to a Country Table? Or should I just make one relationship to a Table containing both Regions and Countries? (I'm thinking for normalization to take the first option, but am not certain)
3. I have a few tables that would link to quite simple data called Gender, it contains two options. 'Male' and 'Female'
For each table that would link to this information; should I have one Gender Table containing this data and relate them all to it, or should I create a separate Gender Table for each instance?
4. In my Players Table I have the option for each player to be carrying something in Both a ‘Left’ and ‘Right’ hand. I've created a separate field for each piece of data in the Players Table. The object being carried in each hand could be the same or different, or require both hands.
For each hand should I create a separate Objects Table containing the same data and then link to it, or is it more efficient to link both fields to the same Objects Table field?
I hope this is clear, but if not I’m more than happy to elaborate.
I have a table that is related to another table one to one. I need this table to be a one to many relationship. When I right click on the link to edit the relationship, I can't figure out what I need to do to change it to one to many. I have clicked on everything and I can't get it to change. Please help me.
Hello to all I am in need of urgent help so any help would be highly appreciated. I will try and explain the problem as easily as I can. The problem is as follows:
1. I have a table of users and each user is mapped to corresponding roles. So in other words one user can have one or several roles. That is one relationship.
2. On the other hand I have each role is mapped to specific module. So we have one module with several roles assigned to that module which is the next relationship.
3. This is relationship that I am having problems with. Since I have a relationship between User to role and another relationship of module to role I want a table that is basically dynamically generated to tell me which users need which modules. So it is a user to module table which the database should figure out according to what roles the user has and which module contains these roles.
I have no idea if there is way to do this or weather the mapping between module to role has to be done manually by me. I would really appreciate any help. Thank You
Im building a web application to control the stock of a small company.
I already made the database with all the items and descriptions in one table.
This table would be the main warehouse. so now i have to create 3 different departments in different tables where i have to move stuff from the main warehouse. So if i have 10 boxes in main, and i move 4 to department1. then i would get 6 boxes in main and 4 in dep1.
My web app would be constantly updating the stuff being sold in departments 1,2,3.... so here is my question.
how do i make the database to update the quantities by itself in the main warehouse table if department X sells anything...?
Like in Excel, when you work with different sheets that can update the other ones if you change a number. the rows can be linked... can i do this in access?
Otherwise i would have to write a lot of extra SQL code in the ASP scripts and im really out of shape cause i don't program in ASP sisnce very long time ago... years.
