Passing Field Values between Tables

[MNM]

Greetings,
Currently, we have a table which contains a field for each type of training that can be taken (FUT1, FUT2, ...). Once an Instructor has taken one seminar, the table is populated with the date taken, via their employee number (the key) through an update form.
Now, the company wants the paper training reports to turn into a digital part of this database.
As envisioned, the form and associated table will have combo boxes with pre-determined training types (FUT1, FUT2, ...). The date would be typed in.
The problem I see is getting the dates and training type from the future table to populate the existing table in the correct field for the correct Instructor.
In addition, there exists a report which prints out the training dates for each Instructor at each school. This is will still be in use.
Any ideas would be gratefully appreciated.
M. McAllister

 

[CJ_London]

sounds like your tables are not normalised so I would suggest you investigate normalising your data first.

In any event, to provide any real help you need to provide more information on your table structure, relationships etc

 

[MarkK]

It's almost certain from how you describe your process that you don't really understand how relational database tables work. I recommend that you google "database normalization", or "database normal forms", and do some research about how to represent objects using relational database tables.

Dealing with poorly structured database tables is worse that building a house on a crooked foundation. Sorry to bear the bad news, but if you want to create a database system, you need to understand database normalization principles.

Hope this helps,

 

[MNM]

Greetings,

Presently, we only keep track of the seminar and date for the Instructors. The table fields are:

EmployeeNumber (Key)
FUT1
FUT2
2IW
PreCourse
Math
Nursery
TOEFLiBT

This was sufficient. Now the management wants to include the old style training reports (Excel ‘forms’) as part of the database, necessitating the creation of new tables, queries, forms, and reports.
I was hoping to retain the old table as a report exists which displays who took what and when. In addition, there are two forms (an update and an info), with sub-forms for the training info, in which the dates can be entered and viewed respectively.
My intent was to just port the date of training to the appropriate field in the existing table for the appropriate Instructor. This way I wouldn’t need to perform an extensive overhaul.
However, from what I’ve read, this is not the best course of action and the overhaul is required.
If it helps, attached is the database populated by dummy Instructor data.

Regards,
MNM

 

[Galaxiom]

However, from what I’ve read, this is not the best course of action and the overhaul is required.

Yep. The sooner you restructure the less time you will end up wasting on kludging.

 

[MarkK]

There's not really any new information in your post #4. There is more detail, but the maker of those data structures, particularly this table . . .

EmployeeNumber (Key)
FUT1
FUT2
2IW
PreCourse
Math
Nursery
TOEFLiBT

. . . is using a database table like it's a spreadsheet, and that's a bit like using a canoe as a flower pot. Yes, the flowers will still grow and everything, but the whole canoe part is wasted. You might was well just use actual flower pots. Or, if it works for you, fine, fly at it, but a database is so much more powerful if you use it properly.

Search Term: Principles of Database Normalization

All the best,

 

[MNM]

There's not really any new information in your post #4. There is more detail, but the maker of those data structures, particularly this table . . .,

I spelled out what I have done and will be doing as clear as possible.

. . . is using a database table like it's a spreadsheet, and that's a bit like using a canoe as a flower pot. Yes, the flowers will still grow and everything, but the whole canoe part is wasted. You might was well just use actual flower pots. Or, if it works for you, fine, fly at it, but a database is so much more powerful if you use it properly. ,

The company I work for uses Excel files as 'data bases'. I knew a little about true databases, but hadn't dealt with them until I made the attached one to #4. I tried to 'normalize' since I understood compartmentalization. I don't want to 'reinvent the wheel' or waste what I've already done; the Training Report is useful.

Search Term: Principles of Database Normalization,

I will look deeper into this starting Monday.

I truly value your time in my guidance.
MNM

 

[JHB]

Take also a look here http://access.mvps.org/access/lookupfields.htm