Record Length Too Long in a Table

[Guest]

I've vetted my db with Allen Browne's dbIssueChecker and in some tables, I
got the message - "Record length too long". So, I'm looking at ways to trim
the length of my records. One possibility that occured to me is:

I've a field in the Main Table that gets its value from another
lookupTable.Five more fields in the main table are updated with values from
the same lookupTable based on the first field. Basically, these six fields
together is a record in the lookupTable. User only enters one field and based
on that, the other five fields are updated to the main table.

Is it good enough to do away with updating the Main Table with the entire
record from the lookupTable and pull those values in my output (Reports and
Form ListBoxes) at runtime ?

Thanks in advance.

 

[Armen Stein]

I've vetted my db with Allen Browne's dbIssueChecker and in some tables, I
got the message - "Record length too long". So, I'm looking at ways to trim
the length of my records. One possibility that occured to me is:

I've a field in the Main Table that gets its value from another
lookupTable.Five more fields in the main table are updated with values from
the same lookupTable based on the first field. Basically, these six fields
together is a record in the lookupTable. User only enters one field and based
on that, the other five fields are updated to the main table.

Is it good enough to do away with updating the Main Table with the entire
record from the lookupTable and pull those values in my output (Reports and
Form ListBoxes) at runtime ?

Thanks in advance.

Yes. That's the whole point of a relational database. Only the foreign
key values should be duplicated from table to table. Use join queries
to put it all together on your forms and reports.

 

[Guest]

I've not given any relationships to the lookuptables, but simply updating the
"data" tables(with relationships) with values from those "lookup"
tables.That's not a good design, I thought. And just got confirmation.

Thank you very much.