This only shows the flow if the main category is "Floors", sub category "Joist", and then the choices under subcategory "Joist". There will be others for the other categories, subcategories, and choices.
Can someone help me or steer me in the right direction in setting up the database table/tables to accomplish this. Oh and BTW, there will be prices attached to each "Choice" under the subcategories.
I hope that this makes sense... any help would be much appreciated.
I am designing a database for my organisation. I have done most of it but am stuck on this. Ideally I would like to have a check box (in a table) that when checked a load of data is carried across from that record to a record in another table.
Given that I can't and don;t want to use VB is there anyway that this can be done easily?
if i had a table with products and i want to keep a record of what has been chaged or added to this product, whilst keeping the old records how could i set it up in a databse?
the excel spread sheet looks like this
product commments
1 chnged this and that 20/08 1 modifyed component 21/08
It's a simple question really. I'm currently learning databases and am doing a project, just to show that i understand everthing i've learnt so far. I have to produce a small database.
There's nothing difficult about the project, and its a very basic database, but i was just hoping to ask a small question.
I'm producing a DVD database, to hold details on a collection. My main table holds the majority of the fields, as follows;
The problem came with boxsets. Originally i was just going to have boxsets as one entry, but some contain a few dvd's, each with different certification, etc, and i wouldn't be able to record running length, director, etc. So i added a ysnBoxset field (just to record whether a dvd was part of a boxset or not) and then made a new table with
lngDVD_ID strBoxsetName
So now i can record which are part of a boxset, and the name of the boxset they belong to. But.. then i got to the problem of Purchase Price. Obviously i cannot record an individual purchase price for those which belong to a boxset, and i want to be able to record the price of the boxset.
So my question is... is it acceptable to add a curBoxsetPrice field to tblBoxsets, which would allow me to store the price... and then just leave curPurchasePrice as £0.00 for those dvd's in a boxset??? Or is there a better way of doing it? (I know there is, but i'm a novice :( )
Thanks for any help you can give, sorry for the lengthy explanation! :rolleyes:
Within my db I have a table, tblProjects which currently has 36 fields. Each project will have a fixed set of 12 tasks, each having a begin and end date as well as a yes/no "completed" field. This would add another 36 fields to tblProjects.
Instead, I have created a new table tblTasks which has these 36 fields along with a PK(TaskID) and FK(ProjectID) and is related to tblProjects. I believe tblProjects is already normalized properly with relationships to tblCompanies and tblContacts as well.
I'm not sure if this was neccessary, or should I have just added the task fields to tblProjects. What, if anything, are the advantages of one way over the other? I'll be upsizing to SQL Server, does that make a difference?
Bit of a long one but I require some advise if people can supply it.
I've started creating a DB that is now getting out of hand due to me being inexperienced. The things I want to do now are getting way to complicated. From reading various posts I know that this is all being caused by my database design and while the DB is still young I'm go back to square one. I want your advice on this if you can to ensure 3 weeks from know I'm again not chasing up weird bits of VB code to make it all work.
I basically have a lot of information to hold that interconnects with each other. I'm making up a role profile DB (so we can assign define access rights to a computer system) I have lots of info to collate but the basic stuff is.
Staff Records (Name, business area & ID) Applications (What computer applications do staff require) Shared Drives (What access to shared drives and folders do they need) Shared Mailboxes (what access to shared mailboxes) Roles (users will be assigned roles to suit their requirements)
Basically what I have at the moment is below.
Roles Role ID Role Name and about 15 other fields that dont really matter for this
Applications Application ID Application
Shared Drives Shared Drive ID Shared Drive
Shared Mailbox Mailbox ID Mailbox
Each role will only have a select number of applications, mailboxes and drives from the overall list. so role 1 may give access to 2 of the 10 applications, 1 out of 5 shared drives and 3 out of 4 mailboxes. Role 2 on the other hand may need 9 out of the 10 applications, 1 out of the 5 shared drives and 1 out of 4 of the shared mailboxes.
I just don't understand how I can create a form from these tables that would display all the different roles with their respective apps, mailboxes and drives they would need.
any advice you can give to help whould be appreciated.
I am designing a db for our Law office. I want to have tables for different types of Civil Cases-ie Divorces, Deeds, Contracts, Personal Injury, Auto Accident, Slip and Fall, Product Liability, etc. The divorce, Deeds, tables are easy but I am having difficulty deciding on the personal injury tables. Heres my dilemna. Can I get away with one or two Personal Injury tables even though there will be blank data fields. For example, I will need a field for the name of the product in a Producrs Liability field. This field will be blank in all other Personal Injury Cases. I know the rule is you don't do that but my alternative is 15-20 tables for every concievable Personal Injury Case- Auto Accidents, Slip and Falls, Fraud, Prouduct Liability, Accounting, Attorney, Dental and Medical Malpractice, etc. This is in addition to other civil case tables, criminal case tables and federal case tables. Anyone have a suggestion?
I am not sure if which I should be using as the main entity for my tables. I am creating a database for hourly information on individual employees. Each employee will have the same types of hours to keep track of (weekly, bi-weekly, monthly etc) I naturally thought to treat each employee as the databases own entity and created fields for each type of hours but hit some trouble when trying to pull queries to compare each employees hourly information against each other to see who is being efficient or not. Each employee has the same exact fields but with just different numbers. We track each type of hour by week (Field One: Week 36, Field Two: Aug 28-Sep 03)This is the first time I am creating a database from scratch. All advice greatly appreciated and TIA :confused:
I have a table within a database and i was wondering whether or not i should split the table into 2 seperate tables.
The layout of the existing table is to record quotation information ie product codes, cost price, sell price, delivery dates available etc and it also contains fields that allow the user to state if the quote has been authorised or declined, when it was authorised and a number of options to explain the reason the quote wasn't accepted.
QuotationID - Primary Key EmployeeID - Foreign Key CustomerID - Foreign Key EnquiryID - Foreign Key ProductCode Quantity CostPrice SellPrice DeliveryDateAvailable Notes Authorised - Yes/No field Type DateAuthorised Declined - Yes/No field Type ReasonDeclined LostPrice - Yes/No field Type LostStock - Yes/No field Type LostDelivery - Yes/No field Type LostCustomerClient - Yes/No field Type LostNoFeedback - Yes/No field Type
above is the layout of the table, does anyone think that it might be a good idea to split this table into two tables, one table to record the quote information and another to hold the authorisation or decline information??????
i am creating a database for a local football club. I want to show player information (the main focus of the database), such as, what guardians are responsible for this player, what are the Doctors details for this player, what team does the player play for etc. I have seperate tables for the Guardian, Doctor and Team information.
I also want to hold Staff details, (Name, address, staff title etc)
My problem is that someone in the staff table, could also be in the guardian table.
Should i combine the Guardian and Staff tables into one table as I dont want to have to enter the data twice for both a staff memger and a guardian
Note: a player can have more than one guardian a guardian can be responsible for more than one player.
What is the best way to approach the design of these database tables.
Have a database that I am working on this is constructed to perform Compliance tracking of wellness activity by employees. Have all my tables, queries and a form that has 3 tab controls as well as a subform on one of the tabs.
It is necessary to create a quarterly report card based on 6 wellness cateogories that have specific criteria. I thought I was OK but now I am having difficulty pulling it all together on the report. I now think that it has to do with my table construction and I am looking for advice. If there is someone I could send my DB to who can take a look and give advise or assistance I would greatly appreciate it. Thanks.:confused:
I'm currently in an internship working solely with databases. I've become really interested in designing databases and I now want to design my own. I was wondering if I explained my table structure then someone could give me their thoughts and ideas for improvement. I have a huge sport trading card collection and I wanted to create a database for it. This way I could run some quick queries to find out how much my collection could be worth, how many cards I have, easily keep track of duplicates. Things like that.. This might seem strange, but I think it would be a good learning experience that would help me utilize many of the features of Access.
My Table Structure:
Ok I have a Company table(Topps, UpperDeck, etc) and they sell many boxsets(which would be another table).. Boxsets have many Cards(which would be my third table)...
Now here is where I get confused. I want have a sports table that would categorize my cards by what sport they are, but I don't know where I could link this. I also have a players table. This table will have a 1:M with Cards because 1 player can have many cards, but couldn't Cards and Players have a 1:1 because 1 card shows one player???
Finally, I want a Price Table that will be linked somewhere, but I've yet to figure out where to link this too.. Have I missed anything???
Your ideas and opinions are greatly appreciated!!!
i have a table(patients) with more than 1500 records.this table contains patients information like diagnosis etc.I use cbo boxes in my form to choose info.(i have separate tables to keep this information e.g.table for diagnosis, table for treatment procedures etc.
of course these info are kept in the patients table as text fields.and also i have many query with criteria to select specific records(for example ) parameter value is [Enter diagnosis] and i type for example "cardiac" to get the list of cardiac patients etc.
now , the size has become large . so i want to do somthing to solve this i designed this when i was very new to access.
how if i want to change the field type from text to number which can look up the required info from other table.
but if i do this , i think that my queries want work .
any advice on this.
i have about ten fields to be changed from text to number.
tblreservation (cottage reservation details) cottage (text) - linked to tblCottage customer (test) - linked to tblCustomer start date (date) number of nights (number) Adults (number) Price (currency) etc..... ReservationID (autonum)
tblCottage (list of cottages available for rental) cottage (text) CottageID (autonum)
I need to add a table structure which defines the price band for each cottage at several times throughout the year, in order to take account of peak holiday periods etc. The price field in the tblReservation table needs to refer to the correct price band based on the cottage and the start date of the reservation.
Any thoughts how best to approach this would be greatly appreciated.
I am looking at creating a database for a charity, to help them maintain there volunteer information.
The database will need to hold information about the charity, volunteers and there roles, language and status.
This is the db design so far.
Branch id PK - charity number name * house * street1 * street2 street3 town * city postcode * p_office * p_land * p_mobile fax email not sure of data type and length www not sure of data type and length
volunteer id PK - unique number, auto number vol_name * f_name * s_name * house * street1 * street2 street3 town * city postcode * p_home * p_work p_mobile email last_change date/time, when record last updated
vol_link_lan vid FK, PK lid FK, PK level qua
language id PK, Auto name *
vol_link_rol id PK, vid FK rid FK sdate * edate *
role id PK, auto name * description
vol_link_sta id PK, vid FK sid FK sdate * edate *
status id PK, auto name * description
I am not sure if the vol_link_rol and vol_link_sta are correct, I have created a PK to ensure there is a record of the volunteer and the status and the same for the roles table.
I have been asked to create a simple 5 question quiz and can not for the life of me figure out the table and form design. The goal is to have a question listed and then 5 answers to choose from. I need the answers to be in an options control format meaning they will read the question and check one of the option boxes for their choice. I need it allow only one of the 5 to be chosen...that is the problem. If I make each answer a field then they can check all of them and I don't want that. I don't think this is that difficult but would like to stay away from coding it as I am very good in access except for the code part.
I now understand that when opening and saving crosstab queries Access (2010) runs that query to ascertain the column names. Unless you hard-code them. Running the query takes at least 20 minutes. I have hard-coded where I can, but one report takes arbitrary dates so I can't hard-code them.
I believe that turning off AutoCorrect might make a difference to whether the query runs - but I don't want to turn it off.
Hi all! Here is what I want to do, and what I have done so far:
I have one table called "AUTOS" This is a table imported from pc file, and tweaked to make it work well in Access. I learned alot doing this, and now have workable forms, queries, and reports being generated on this table. I learned on here not to let my users "work" with the table, only through forms. So that all works very nicely!
Here is the next step. First a simple background: We are a Used car dealer. Table "AUTOS" contains rows, each one consisting of many Fields. The main one being "Stock NO". Then all the remaining fields are vehicle info (many fields, but all relating to the vehicle type etc), cost, sales price, etc.
What I want to do is create a new table, called RECONDITIONING. In this table I want to store everything done to a vehicle after purchase. For example, if we purchase a vehicle, then change the oil, put on new tires, and detail it, I want these items in the reconditioning table. But I want them to remain linked to the "correct" stock number in the main table.
I believe I have done this, by doing this: I created a second table called reconditioning. Added the fields I wanted, the first one being "Stock NO". I made "Stock NO" in the main table autos the primary key, and then opened relationships, and linked the reconditioning table to the main table via that field.
It appears to have done what I wanted too, because if I open the reconditioning table, and type in a vehicles stock no, then the reconditioning info, then go back to the main table, there is now a + next to the row. If I click this plus, a box drops down with each item I added to the reconditioning table. So far so good!
Here is the main question: Now that I have this info in what seems like the proper fashion, how do I work with it?
I need to create a form, containing elements from EACH table. The design I have in mind is like this:
Across the top, I want vehicle info:
Stock No Year Make Model Date In Cost 5922 1994 Ford Focus 1/1/05 1000.00
Then under that, I want a "table" in a form, which pulls from my "reconditioning" table, listing each item that has a stock No that matches the one on that record:
Ok, now, I want to allow my users to add to that on this form, to type in new entrys. I think I got the idea how to do that, but suggestions are welcome. Now, on this form, I want at the bottom, the following:
Vehicle Notes: (Just a text field for "notes" on a particular vehicle)
Total Reconditioning cost: (this is a field on the FIRST table, AUTOS, that I want to calculate by adding the total from the list above, IE in this case, 95.00)
Total_ACV: This is a field from the first table as well, which I want to calculate using (Vehicle cost: Which is in the first table)+(Total Reconditioning Cost: which is above)
Like I said, I think I have the table layout and design correct, I am just not sure of how to work with values in linked tables like I have done, and I am not sure get the right info in my list on the form, then add the totals properly.
Hi! I have the following problem: I'm developing a database for a transport and logistic firma. They want to have in the main Database the following fields: Relation(From Where To Where the Transport is being made), and Transit (the countries through which the truck goes). The Relation must be in fack two fields: From, and Destination. Next based on the choise made in Relation, in the field Transit must show the known destinations. Can someone help me solve the problem?
I currently have a DB ( which runs good) with a table called RMAOptions. This table contains (by column) lookup data for list & combo boxes, IE.
column 1 = TECHID column 2 = STATUS column 3 = so on and so forth
Is it cosidered acceptabe to have a table like this or should each column be in its own table. I don't have any problems with this now, just wondering if there might be some in the fuure?
Recently I'm helping a friend to convert his MS-Excel spreadsheet into MS-Access. I met a problem and need some help on defining the table fields.
In one of spreadsheets, he gets 3 columns, the 3rd column values is calcuated by a formula based on the previous two entries as the followinf: D3= C3+B3
When I tried to turn this table into MS-Access design, I don't know how to define the 3rd column (field).
Is there any chance I can set any expression/formula for 3rd field in the table defnition to retrieve data from previous columns( I don't want to design this function in the query)?
I'm trying to create a validation rule in a microsoft access table that would require the entering of data in a "comments" field is another field's check box has been checked. What is the best way to go about doing this?
Hi I have been struggling for quite a wee while thinking the design of a part of my Database, it is maybe not that complex but seems quite difficult to me... :o I have different ASSEMBLIES made of differents PARTS (Bodies, Straps, Hinge, Screws...) and most of them are built on the same models but there is quite a few odd ones. Most assemblies are made of 1 Body, 2 Straps, 2 Screws and 2 Hinge pins but some can be made of 1 Bodies, 2Screws and 2Hinge pins only or 1 Bodies and 4 Screws there is quite a few configuration and some can be made of really unusual parts that are only gonna be used once or twice.
There is different models for each part So I have created TblStraps, TbleScrews, TblHinge..., Tbl Miscellaneous (regrouping all the odd ones)
This is where I am getting confused because I want to make it easy for the user to fill in a new assembly detail.
Each assembly is defined by is body,
and I could use a query to show the number of parts for each AssemblyModel. Should I have a table for each assembly model as shown below:
TblModel1:............................TblModel2:.. ........................................... BodyId (Primary).....................BodyId (Primary).................................... StrapId (linked to TblSrap)........ScrewId (Linked to TblScrew).................. ScrewId (Linked to TblScrew)....HingeId (Linked to TblHinge).................... HingeId (Linked to TblHinge)
and a table for the miscelaneous models who is going to have quite a few fields because some of those models can have 1 or 2 types of srews and Hinge pins and up to 8 more parts, lots of the Records will have blank fields as well. :confused: Ohhhh, I don't know where to start, I am confused and needs some advice, I feel bad to beg but I am really desperate :(
Hi Guys, thought i would pick your brains to try and help me figure out how to build this database. Any help would be very much appreciated as this one is making my head spin.
Brief::
I need to create a database that will hold information about our suppliers and the products that they stock and make.
One supplier can have a number of contacts that we speak to. The supplier produces a number of different products. Each of the suppliers stock certain items in certain sizes and weights and make the remainder of their stock to order, so each supplier has a number of different supply options. So in addition to the multiple supply options their are multiple sizes & weights, as well as multiple qualities.
dont know if this helps people to understand buit the products we are talking about is paper (sheets or paper & reels of paper)
example.
Joe BLoggs (Supplier) has 3 sales members (Louise, Maggie, Sue) this supplier holds some sheets and some reels in stock (Stock Sheets, Stock Reels) but they also make sheets of any size and weight between a certain range as well as reels (Bespoke Reels, Bespoke Sheets). These sheets and reels can be of different qualities (gloss, silk, offset). These different qualities can have a number of different grades (Manhattan, Triumph, Charter) and will be available in a number of different weights (70gsm, 115gsm, 150gsm).
The idea behind creating the database is to allow the sales team to query the database to find a supplier that can match the customers criteria.
I have created the following database tables
tblMainDetails AccNo (PK) SupplierName Address1 Address2 Address3 Address4 PostCode Tel Fax Web Email
tblContacts ContactID (PK) FirstName LastName Tel Email
