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

[Cicada]

My original table 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

Now, should I break this table into 5 (One index with one translation only)
?
Which Table Format consume less memory?
Which Table Format run faster?

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.

 

[KARL DEWEY]

There are some folks that probably can give better advice than I but it seems
that you need a table structure like this --
Book_Index Language Translation
<Integer> <Text> <Memo>
With the Language specified such as English, Greek, Latin, etc.

Or use a number, long integer field related to a reference table of Languages.

Then you would append from the existing table to the new one.

 

[Cicada]

Thanks for your reply.
I will have another table to register th language for different column /
table.
But my below main point is: Which table format is more optimized?

For 1st Table, it is good for later mulit-version 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.