Should I break down this kind of Table? >.<

[Cicada]

1st table'sFormat is like this:
Book_Index Translation1 Translation2 ... Translation5
<Integer> <Memo> <Memo> <Memo>

There are total 40,000 records x above 6 fields.
Number of Translations are always fixed and equal for each record, not
variable.
Importances of each Memo are equal.

In my Form & Report, I will output both format:
1. Index + Single Translation
2. Index + Multi Translation

2nd Format:
Break 1st table into 5 tables (One index with one translation only - 2nd
Format)

For 1st Format, it is good for later multi-Translation output, since I only
need to do index-matching by once, not "multiple". This speed up the
operation.

But I am not familiar with internal operation of Database & SQL. Will they
load WHOLE table during each operation (searching, ...), or just load my
assigned fields?

If former is the answer, then 1st Table will consume too much memory and may
conversely slow down the operation.
Then, I can only choose 2nd Table"s" format.

N.B. I am using an application similar to MS Access, but it can access one
Database in the same moment only. Therefore, all Tables and Forms are always
stored in the same file.

 

[Terry Kreft]

To me both your structures are wrong.

You should have 2 tables

Table1: Books
Book_Index (PK)
Book_Title
etc.

Table2: Translations
Book_Index (PK)
Language (PK)
Translation