"Mark Hanley" <mh*****@SpamblocKclara.co.uk> wrote in message
news:10****************@dyke.uk.clara.net...
I am trying to add records to both tables using this one form. The Pupil
table holds general student information such as names etc.. The SEN table
holds further information about a student's educational needs.
I have information from each table separated onto two tabs on one form
except that the UPN from the SEN table (the key on which the two tables
are related) does not appear on the form at all.
There is a 1 to 1 relationship between the two tables.
I hope this fills in the picture a bit. Thanks for helping.
Mark.
"Fletcher Arnold" <fl****@home.com> wrote in message
news:bm**********@titan.btinternet.com... "Mark Hanley" <mh*****@SpamblocKclara.co.uk> wrote in message
news:10****************@dyke.uk.clara.net... I have found similar problems to mine on this and other newsgroups but
I still haven't been able to solve my problem...
I have two tables 'Pupil' and 'SEN' which are related on a field
called 'UPN' (unique pupil number).
I have a form which is bound to a query that is drawn from both of
these tables and contains Pupil.UPN but not SEN.UPN aswell.
When I update the form I get the error 'The field SEN.UPN cannot
contain a Null value...'
Can anybody give me a hint as to what I need to do to put this right? I'm tearing my hair out here!
Thanks.
Mark Hanley
You haven't given us much of a clue as to what is contained in the table
SEN, what type of relationship is between the two tables and what is the
purpose of the form in question? Are you trying to add a new record?
Do you expect to be able to add records to both tables from this one form?
Sometimes a form which is based on two tables, is not a logical choice
for making additions - have you considered a form/subform combination?
Fletcher
The first suggestion would of course be to put all the student data into one
table - tblStudents. That would solve your problems in one hit. One to one
relationships between tables are really to be used in special
circumstances - perhaps you have implemented user-level security and you
want to hide some sensitive data in one table but let other data be more
visible. Or perhaps you have found a need to use sub-classing.
However I have only found the need to use them once and, by strange
coincidence, this was a database holding student records.
If you really do have a pressing need for this one-to-one relationship, then
by far the easiest way would be to disallow additions in the standard way -
the record selectors at the bottom of the form. Create custom buttons for
this.
Fletcher
