Could someone please share their opinion with me on the following:
I have a database with a Table which stores People's details, e.g. ID, Name, Surname, ...., etc (e.g. tblPeople) .
Now I have people filling out a questionnaire, of which the results I want to save in an Access table. Each person will fill out this questionnaire only once. The number of fields I will need to accomodate the answers to questions asked, is around 120. For example, an answer to Question1 will appear in a field called Q1.
I know that the limit for fields in a table are 255, and my total fields in tblPeople so far are about 20.
Should I keep Q1 and all other fields in the same table as tblPeople, or create another table to hold all answers and create a one-to-one relationship between tblPeople and tblQuestions&Answers ?
Can someone give me a tip, in particular if this will cause performance problems?
I have attached a word doc showing my table relationships. I would like an opinion on as to whether it is normalized correctly. It is for a bowling league that has 10 teams and 50 bowlers. The team names, lane assignments will change every year and the bowlers will be on a different team from season to season. Also the tblScores is set the way it is because some bowlers will show up late or injure themselves so because of the awards that are handed out at the end of the year for high scores, perfect attendance etc. this is how I thought it would work best. I wanted to make sure before I put all the bells and whistles in. Thanks in advance.
I manage academic papers whom are written by multiple authors and reviewed by multiple reviewers. Currently, all the data is stored in one big table and I'm not able to get any statistics or real tracking out of it.
I have set up a test DB with 3 tables so far:
Main Table_ID -auto sequential key CORP_ID -internal paper id STATUS -open, overdue, accepted, rejected REC_DATE -received date MOD_DATE -record last modified date TITLE AUTH1_ID -linked to Author.ID AUTH2_ID -linked to Author.ID REVR1_ID -linked to Reviewer.ID REVR2_ID -linked to Reviewer.ID
Author ID -key field NAME DESIG -designation EMAIL PHONE
Reviewer ID -key field NAME DESIG EMAIL PHONE RATING
My goals are these:
Create a module that manages the authors. They are usually the same group of people. Each author should only appear once.
Create a module that manages the reviewers. Also, usually the same people (but different than authors). Each reviewer should only appear once.
Create a main form that allows the end user to add a record (paper), assign author(s), assign reviewer(s).
Create Query/Report that would then be able to: - track authors and their papers - track reviewers and their reviews - as well as track papers and their authors/reviewers
When I create subforms, they appear to be 'backwards' meaning that the Author form tends to be the main form and the Main form tends to be the subform. I think this is b/c the Author.ID field is the key field, whereas the Main.TABLE_ID is the key field, but not relevant for other than keeping things straight, nor is it related.
Can someone point me in the right direction?
Alternatively, has someone created a database like this already that I can buy? :)
Firstly, I want to admit that my knowledge about data base construction is fairly basic. I am trying to build a data base for humanitarian projects that do not at all resemple of the usual examples including customers, invoices, suppliers and what have you. My problem in constructing the DB is that most of the projects will address more than one subject and also include more than one target group and even operate in more than one country. In my first attempt I filled the relevant fields (subjects, target groups and country) with more than one value using a form with multi select lists. The problem was that it was very difficult to query these multi-value fields and kind people in this forum strongly advised my to reconstruct the DB avoiding such fields. What I need is to be able to view/print various selections based on precise criteria that include a region (or country), a subject and a target group in all kind of combinations. The problem is to decide on what tables to establish and their interrelation. I guess that when entering a project record (using a form) I will have to store somewhere what subjects (could be more than five) and target groups the project include. It is, of course, not a problem to establish special tables or value lists for the subjects and target groups and countries, but where/how do I store the basic project information for a project and the multi-values that are related to the individual project? I hope that this is not too confusing and I would appreciate any suggestion for a simple table structure and the interrelation between the tables. Many thanks in advance. Niels
hi everybody, great resource you have here! my employer is tracking around 250 pieces of data for each client at our facility. i am making a new access system based on their existing mysql database and web front end. before i start messing around with forms and reports, i want to see how well this existing structure will work in access, and what kind of approach i should take. i am a newbie with access, but lots of experience with asp/mssql/php/mysql. making web forms is so time consuming that i figured i would be best off moving the whole thing to access and starting from scratch.
client information is stored in eight tables. each table has around 30 fields in it. the first table has a primary key autonumber, and the other seven tables have foreign keys with unique constraints that point back to the first table. that is, for each client record in the first table, there can only be exactly one corresponding record in the other tables.
i did some data massaging, and got the eight client tables into one big table, but the resultant table has almost 250 fields in it, and access doesn't seem to like working with tables that big. so i am thinking that it is best to leave the eight tables separate, but linked in one to one relationships.
i was kind of ideally visualizing a form with eight tabs so that i could edit/update all of the information from the eight tables rather seamlessly.
my question is: what approach to table structure will best suit my needs, and what approach should i take to add/update/delete the info with forms? will i need to do vb for this? any good one-to-one example databases anybody could point me at?
I was contacted today by a staffing agency and was told that I looked like a good fit for a Data Analyst position. The agency and wanted some more information about my resume and wanted me to email them my references. Next step I would assume would be an interview.
I did want to post the responsibilities of the job and see if other DBAs thought it looked like entry level work. The only thing I know about the company is that they are automotive and pay is under 40K. I have been trying to break into IT for the past few months and this looks like a great opportunity. :) I appreciate your comments. -Jon
Scope of Work:
Provide analysis support for the following: reduction of engine warranty costs, improvement of field reliability, identification of root causes, and development of new data systems. Position also monitors and reports effectiveness of actions taken.
Perform data analyses in support of problem-solving teams and management decisions, to include identification of root causes, determination of population(s) affected, failure rate estimates and projections, and estimated warranty impact.
Play a supporting role in the development of new custom-built data systems aimed at informational support of warranty analysis and reducing the time and cost of doing business.
Maintain SQL Server and Access databases of supporting information for reliability analysis to include: warranty claim information, failure modes, product improvements.
Support maintenance of custom warranty analysis software (RAS); includes troubleshooting data issues, updating information tables, and checking validity of system data. Other Projects as assigned.
If I just want to display a relationship between two tables or more with a form and a subform, and I don't want the users to edit/delete/add the data - just view it. What is the best way - queries, bound forms etc? I created a form with a subform, but then ran into problems because I don't want them to be updated, only viewed.
I have a table that contains 4 columns: index (w/ auto generating number), timestamp, current user, and notes. The notes column is a Memo data type and is used to capture free-form notes typed into a text box.
I would like to display all notes typed by a specific user and do it in a single control, preferably a text box. This way someone can look back over time and review all the notes they typed / added to this table. Is it possible to display multiple rows from a table in a single text box or do I need to use a list box?
I am looking to build and Overtime tracking form and have been pondering on the design of it. Here is my idea and not sure how I should go about doing it (straight forms and tables or queries). I would like to select my employees in a combobox and have their information autofill the remaining fields and/or add new ones. Additionally have fields that I can input any overtime occurred which would be stored in a seperate table but displayed in a sub-form in datasheet view. These fields that were just filled out with the overtime information would clear everytime the add record button is hit.
I know that sounds like alot and sure I can muddle my way through that part of it, the big question I have is do I need a seperate table for every employees overtime? Or is there code/query that can select the records of the selected employee and display the information that pertains just to them?
Has anyone come across or posess a sample database similar to this? If not can someone point me in the right direction for example code and tutorials?
I'm trying to copy the structure of a table to make a temp table. I'm using CopyObject (which also copies the data). So when I delete the data from the temp table, it also deletes data from the source table. Is the data linked? It should just be deleted from the temp table. Below is the beginning of the code. I've stepped through, and at the last step shown, the data in the source table deletes.
Code: Dim strFile As String Dim temp As String Dim tbl As String Dim db As DAO.Database
I realize that this issue has likely been beaten to death in past threads; my recent participation in one brought this issue to light.
Can I get a general feeling from participants concerning the dangers involved in the practice of compacting and repairing databases on a server? I greatly respect the advice I get from these forums, and those who give it, however there seems to be some disagreement between people on this issue.
If there is a danger of loosing records, why does this occur? Are there versions of Access where these problems are solved? Do you think that frequency of use, or volume of data have anything to do with the risks?
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!
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?
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 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.
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
Hello, I want to fix a database I built and I needed some help on the table structure since its saving the data and not the ID number. I have it done and it works but its not correct since I dont understand normalization very well I took the easy way out and now its killing me and I want to fix it. Please take a look and give me some advise or show me a structure on what I need to do to normalize the DB... This would be my first DB so bare with me....
The comments section of each category will have a list of positive phrases and negative phrase equal to the subject like Safety, Quality, Quanity ect. "I didnt pur the phrases in each table yet"
I'm creating a simple db to stor project details. Each project has a unique name, and is part of a programme. Each programme name (ie SIG023) can have multiple projects. these projects recieve numerous support plans, guides and tto plans. I also want to store comments on each project.
Does my relationships and table structures look ok? am i starting in the right lines?
Good morning,since this is my first post I hope I'm not making to many mistakes.I'm making a database for school in Access 2003. In this database I have 2 parts.. A part for Patch connections and a part for PC repairs. The PC repair part is doing okay. The patch part is where I'm having some trouble.I don't exactly know how to start with it, and I'm hoping someone here can help me out.The form, I want to make based on tables should look something like this:A ComboBox filled from a table with about 10 entries in it. (Patchkasten)A textfield in which I have to enter something like this: XX-00 (x stands for alphabetic - 0 stands for nummeric)(Patchnummer) This will have around ~3000 entries.Those 2 should somehow be connected in a table as 1 field. (if that is possible offcourse)If not, is there another way to do something like this, because the combination of (patchkasten)and(patchnummer) has to be unique.. And at last a combobox (ruimte) with around ~ 150-200 entries.Now my question is if someone could help me setting this up somehow. Help would be appriciated.Thanks,F3dde
