Subform does not add record into table2

T

TxHookem45

I have created a quality review database using access. There were to many
fields which needed information to capture, so I exceeded the capacity of
table 1. I built a 2nd table to house the remaining 11 fields needed.

I used a tab control for my input form. There are about 7 tabs of which 1
tab has a subform embedded in the form which contains 9 fields from table2.
Now, the fields is this subform are optional... it only applies if there are
multiple items being reviewed for the same project. So basically sometimes we
could have just 1 item (which means no entry in this tab) and somtimes we
have 10 items which means this tab would have 9 entries in it. Once the
record is saved the database creates the record in table1 and here is the
problem, IF there is an entry in the subform it creates a record in table2
(relationship is Project# in both tables). However, IF there is no entry in
the subform then the record is only created in table 1 no record is created
in table 2. While this may seem ok, my problem is when I generate a report.
Since there is no record in table2 (because no entry was made) the report is
completely blank. The only way I can get it to generate the report is if I
manually select one of the radio buttons on that subform. The system will now
create the record in table 2 and allows me to generate the report.
I tried making fictisious default fields that can't be sent just so an entry
can be made on the subform...but so far it will not generate the actual
record in table2 unless there is a manual entry into the subform.
I have addressed all the Master and Childlinks and the relationship. I just
can't figure out how to force post a record into table2 when there is no
entry in the subform but a record exists and is added to table1. Hope I have
not confused the issue.
Any suggestions?
 
B

Beetle

The maximum number of fields allowed in an Access table is 255.
However, in a properly normalized application you would never have
anywhere near that many in any one table. If you have exceeded this
limit with one of your tables, then you are driving headlong down the
road to disaster. The problem you're having right now is only the
beginning of a long list of problems you are going to have trying to
get any useful information out of your db.

I recommend you do some research on relational design and
normalization. Here are a couple of good resources that you can start
with;

A tutorial by Crystal
http://www.allenbrowne.com/casu-22.html

Allen Browne's Access Tips
http://www.allenbrowne.com/tips.html

The Access Web
http://www.mvps.org/access/
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top