You should not split out fields unless you data needs to be normalized. I
would bet that lots of fields usually means that your design need to be
carefully looked at.
So, I would NOT split fields out just because you have lots of fields. Only
split fields out to normalizing your data.
Here is some reading on normalizing:
ACC2002: Database Normalization Basics
http://support.microsoft.com/?id=283878
Database Normalization Tips by Luke Chung
http://www.fmsinc.com/tpapers/genaccess/databasenorm.html
Data Normalization Fundamentals by Luke Chung
http://www.fmsinc.com/tpapers/datanorm/index.html
324613 - Support WebCast: Database Normalization Basics
http://support.microsoft.com/?id=324613
tables? Enforce referential integrity just give me error, when I try to
enter record which id don't exist in master table.
That is exactly how RI is suppose to work. If you have a one to many
relationship, you MUST first create the "one", or the so called parent
record. You then can add child records (the many side). Each child record
will thus have a field that you set to the parent table. If you use a
sub-form, then ms-access WILL set this field for the relation automatically
for you. If you don't use a sub-form, then YOUR CODE or YOU has to set/enter
the value of the field in the child record that relates back to the parent
table.
Hence, you cannot add child reocrds without first adding the parent record.
There is no other way that this could work...