well ... i finally got the go ahead! thanks for all the advice! So from many different tables for many different semesters I went to one single table for all students with an additional column for describing the semester ... I also made the database first normal by creating a different table for...
I see and understand the point that all you enlightened people are trying to make ...
It's just that this is the way that it's being done historically ... just data entry ... no forms, no reports, no queries ... just basically data being stored and using mail-merge in word to print out simple...
well they don't have the same data ... just the same fields ... so i have a table by the name of the semester having the same structure as the previous semester table but different data (since each semester, different people get admitted ... unless of course a previous semester guy doesn't...
Hi,
I have a database that has around 12 tables. All these tables have the same structure (same fields) ... its actually an academic database with a table containing student info ... one for every semester ... What is the relationship that I should use to define these tables??
- Vick
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.