Maximum added controls over lifetime of form

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

In Access 2000, the specification states that the Number of controls and
sections you can add over the lifetime of the form or report is 754. How can
I know if I have reached the limit? Is there any way to reset it (as by
making a copy of the form)?
I'm guessing that my specific problem may be related to this spec. I have a
complex main form with ten subforms, each with its own table linked by the
child/master field relationship. All of them work fine and have been doing so
for years. The last one that I added usually works, but sometimes the main
form comes up with an error that states that the required field cannot be
null - referring to the child link field. I have tried unsuccessfully to trap
the error. Any hints?
 
In Access 2000, the specification states that the Number of controls and
sections you can add over the lifetime of the form or report is 754. How can
I know if I have reached the limit? Is there any way to reset it (as by
making a copy of the form)?
I'm guessing that my specific problem may be related to this spec. I have a
complex main form with ten subforms, each with its own table linked by the
child/master field relationship. All of them work fine and have been doing so
for years. The last one that I added usually works, but sometimes the main
form comes up with an error that states that the required field cannot be
null - referring to the child link field. I have tried unsuccessfully to trap
the error. Any hints?
Click to expand...


create a nwe control, it will get a number and this is the internal
count.

But this isn't your problem.
your field (the child link) is null and in the table you have set it
to Allow Zero Length=No
 
Thank you for your reply.

You are right that the child link has become null and that the underlying
table does not allow null in that field. The reason for the latter is that
this field is the foreign key. What could cause that field to become null?
When the form is open, the new line on the subform shows the foreign key even
without entering the new line as it does for all the other subforms. For some
reason, this form sometimes loses it and then even without being on that
subform, an error is generated when going to another record. I hope you can
shed some light on what is happening.
 
Thank you for your reply.

You are right that the child link has become null and that the underlying
table does not allow null in that field. The reason for the latter is that
this field is the foreign key. What could cause that field to become null?
When the form is open, the new line on the subform shows the foreign key even
without entering the new line as it does for all the other subforms. For some
reason, this form sometimes loses it and then even without being on that
subform, an error is generated when going to another record. I hope you can
shed some light on what is happening.
Click to expand...
I guess it's a timing problem, one of your field/controls gets
calculated to late.

I seldom use master-child relations , I set the controlsources of
subforms (SQL's) after updating the master-field.
 
Back
Top