Transfer Data on to the wrong way

[carfj1]

Pardon our ignorance....

We have a Tree BIG tables with information about courses:

PersonalData:
ID, Name, etc..

Education:
id, curse1Name, curse1Score, course2Name, curse2Score...Curse80Name, course80score

Training:
id, curse1Name, curse1Score, course2Name, curse2Score...Curse70Name, course70score

All this tables have 8000 rows. (So you can imagine our problems...) The database is Splitted with more than 110 frontusers.

We have decided to change the last to tables to a more relational efficient table system:

CursesNamesTbl:
&
PersonalID&CourseIDTbl:

To change this we have already made the process to change for the WRONG SYSTEM to the CORRECT ONE*. This was implemented using Append Queries changed manually.
*This was done only on a sample database.

Now the real problem:

We would like to enter new data in the new system and append it on the old one.
This will buy us time while changing from one system to the other.

I know this has to be made using a not so complicated procedure, but still I am a very novice VBA technical user.

This is the update query that I would like to have in a module changing CourseName and CourseScore depending on IDCurso.

UPDATE [CURSOS DES] INNER JOIN CURSOS_POR_ASOC ON [CURSOS DES].ID = CURSOS_POR_ASOC.ID SET [CURSOS DES].[Valores 1B] = [CURSOS_POR_ASOC]![FECHA_CURSO], [CURSOS DES].[Cali Valores 1B] = [CURSOS_POR_ASOC]![CALI_CURSO], [CURSOS DES].ID = [CURSOS_POR_ASOC]![ID]
WHERE (((CURSOS_POR_ASOC.[ID CURSO])=9));

I will appreciate your suggestions,
Thanks,

Carlos

 

[beetee]

I'm not sure if I'd take the approach of attempting to update two different databases from the same forms.

It's fairly simple to normalize a database, it's more difficult to write out data in two different table formats in EVERY place your application changes data.

It should be a fairly simple matter to write queries to first pull out data to be normalized, then to join existing tables with the normalized tables to output the normalized tables.

I would suggest you simply get the conversion process automated, perform an initial conversion, test the heck out of it, then perform the conversion again to build your production database.

 

[beetee]

I would like to add that if you run into specific problems translating your information, please post specific details and someone here will be able to help you out.