help to start a project for school

[qupe]

hi
the main idea that i have user form to start my main table , i will choose grad then it will make filter to all student in the same year then it will make filter to all subject of that year then it will give me pre-entered codes related to that subject and each of these code has multi papers it it .

and Of course each one of these fields has a pre-enterd list


so what do you sujjest as main table and relations ?

 

[plog]

That's not how database construction works. Forms are the last consideration. You set up your tables based on the data you want to capture, you build queries/reports to generate the output you want, then you work on forms to allow data entry.

So, to know your table and relations we would need the data you hope to capture. I suggest making a big spreadsheet of all the fields you want to capture along with some sample data for each. Then, read up on normalization (https://en.wikipedia.org/wiki/Database_normalization) and give structuring your tables a shot. Finally, set up your relationlships in the tool and post a screenshot of that. With that we can help you identify issues.

 

[jdraw]

You might try working through this tutorial 30-45 minutes. You will learn the basics of database design. You have to work through it, but you will learn a technique that can be used with any database.

Good luck.

 

[qupe]

hi
i did the relation and the form like shown before but when i choose the code to enter it in the main table it does not work it say " it cannot be edit it bond to expression "

this is the relations

i appreciate any help

 

[jdraw]

I suggest you you work through the tutorial I recommended in post #3.

Start with a clear description of the "business" in simple plain English.

For reference, I am posting the following which is included in the tutorial from RogersAccessLibrary.

The Hernandez Process In A Nutshell:
One of the best database design books of our time is: Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design By Michael J. Hernandez.

Unfortunately, Hernandez goes into such great detail at times that the overall picture is lost. The following is a list of the major steps in the process. This list should not be use in place of reading the book. It is meant only as an adjunct to it.

1) Create a narrative that accurately and in some detail describes the business
2) Double underline each Subject and Direct Object in each sentence
3) Single underline all the rest of the nouns that describe the subject or direct object
4) Make a list of the Subjects. Try to determine which are duplicates or are not pertinent. This will be your Subject List
5) Make a list of the other nouns. Try to determine which are duplicates or are not pertinent. This will be your Preliminary Field List (PFL)
6) Group the fields in the PFL into logical groupings. Do each of these groupings have a corresponding value in the Subject list? If not, you missed a subject so you should add it.
7) Go through the revised Subject list to see if there is any data that you should be storing about that subject that you are not. If so, add it to the field list.
8) Place all the Subjects across the top of a sheet of paper and write the corresponding fields below them, check them off the list as you do.
9) Now look at your tables and fields and compare them to the Ideal Table and Ideal Field:

Elements of the Ideal Field
--------------------------------------
It represents a characteristic of the subject of the table.
It contains only a single value
It cannot be deconstructed into smaller components
It does not contain a calculated or concatenated value
It is unique within the entire database structure
It retains all of its characteristics if it appears in more than one table.

Elements of the Ideal Table
----------------------------------------
It represents a single subject
It has a primary key
It does not contain multipart fields
It does not contain mulivalued fields
It does not contain calculated fields
It does not contain unnecessary duplicate fields
It contains only the minimum redundant data

10) Create Primary keys and identify any Alternate Keys (see Hernandez)
a) Note: Most tables will have Artificial Primary keys (Autonumber in MS Access).
b) Alternate keys are used for Unique Indexes.
11) Identify relationships between the tables. Be sure you can identify it in both directions:
Each Customer can have One or More Orders
Each Order can pertain to One and Only One Customer

12) Resolve any Many-to-Many relationships with the addition of a Linking table and two One-to-Many Relationships.

Order >----------------------< Products
(Each Order can have Many Products)
(Each Product can be on Many Orders)

Order ----------< OrderProducts >---------Products

13) Create your relationships, put the Primary Key of the table on the "One" side into the table on the "Many" side.

One-To-Many 
Customer		 	Order 
--------------- 	---------------- 
CustomerID (pk)------| 	OrderID (pk) 
CustomerName        |-------< CustomerID (fk) 
...other fields 		OrderDate 
...other fields

Many-To-Many
Order		 OrderDetails		     Products 
---------------    -----------------	     ---------------- 
OrderID (pk)--------<OrderID (cpk)(fk)              |---- ProductID
      OrderDate          ProductID (cpk)(fk)>------|     ProductName
...other fields				    ...other fields

Good luck.

 

[NauticalGent]

gupe,

Pardon me for putting in my unsolicited two cents. Without a face-to-face conversation, I can only make assumptions, so please grant me a pass if I am off-base here.

Many times, people new to Access come here and want a quick answer and do not heed the advice given by people like plog and jdraw. Bad mistake. Access is definitely the right tool for what you are trying to do. Sound table structure is VITAL to any database application. The best advice to anyone starting out is to take the time and learn DB normalization.

Without it, you will find yourself making time to do things over because you didn't take the time to do it right the first time.

Again, if I read you wrong, I apologize.

 

[qupe]

Sorry for every one to be newbie

gupe,

Pardon me for putting in my unsolicited two cents. Without a face-to-face conversation, I can only make assumptions, so please grant me a pass if I am off-base here.

Many times, people new to Access come here and want a quick answer and do not heed the advice given by people like plog and jdraw. Bad mistake. Access is definitely the right tool for what you are trying to do. Sound table structure is VITAL to any database application. The best advice to anyone starting out is to take the time and learn DB normalization.

Without it, you will find yourself making time to do things over because you didn't take the time to do it right the first time.

Again, if I read you wrong, I apologize.

thank you for super polite language Mr NauticalGent .

the thing is by the time needed to understand access fully the need of the " help " will be useless


again i apologize sincerely

 

[The_Doc_Man]

If you are doing this for a class, the instructor for that class should have demonstrated some basic steps for you. Here is the problem you will have. If you use stuff that you got from the web and didn't use methods taken from the class, the instructor would have every right to argue that you weren't paying attention in class in the first place. Before you look for someone else to do your work for you, it would be a good idea to determine the instructor's viewpoint on the kind of help we offer.

 

[qupe]

If you are doing this for a class, the instructor for that class should have demonstrated some basic steps for you. Here is the problem you will have. If you use stuff that you got from the web and didn't use methods taken from the class, the instructor would have every right to argue that you weren't paying attention in class in the first place. Before you look for someone else to do your work for you, it would be a good idea to determine the instructor's viewpoint on the kind of help we offer.

Sorry for misunderstanding but i work as Students Affairs employee and this report is asked from me .

the thing is i do all my job on Excel but as you know it has limit not like access.

 

[NauticalGent]

Try this for some information:
http://fmsinc.com/MicrosoftAccess/DataAnalysis/versus-excel.html