T
Tom Waitman
I have a form that has two synchronized subforms. One of the subforms is a
continuous form that shows a single line summary of each record. The other
form is a single record form that shows the corresponding detail record.
The forms are synchronized by using the Set subform2.form.recordset =
subform1.form.recordset command. This works really well, and changes made
in one form are shown in the other. As I scroll through the continuous
form, the detail form follows.
The problem is with check boxes. While I can change the text in text
fields, combo boxes, etc., when I click on a checkbox, for some reason the
form immediately tries to execute an form_BeforeUpdate event and then after
a long pause, Access closes with an error, asking to report the problem to
Microsoft. I have tried it with a variety of forms and tables, always with
the same result. Everything works perfectly, except for checkboxes. If I
run the same application under Access 2000 rather than 2002, it works fine,
so it is apparently a 2002 problem. I'm running all of the latest service
releases for Windows 2000, Access, and SQL Server.
Any ideas of what the problem is or how to work around it?
Thanks in advance,
Tom
continuous form that shows a single line summary of each record. The other
form is a single record form that shows the corresponding detail record.
The forms are synchronized by using the Set subform2.form.recordset =
subform1.form.recordset command. This works really well, and changes made
in one form are shown in the other. As I scroll through the continuous
form, the detail form follows.
The problem is with check boxes. While I can change the text in text
fields, combo boxes, etc., when I click on a checkbox, for some reason the
form immediately tries to execute an form_BeforeUpdate event and then after
a long pause, Access closes with an error, asking to report the problem to
Microsoft. I have tried it with a variety of forms and tables, always with
the same result. Everything works perfectly, except for checkboxes. If I
run the same application under Access 2000 rather than 2002, it works fine,
so it is apparently a 2002 problem. I'm running all of the latest service
releases for Windows 2000, Access, and SQL Server.
Any ideas of what the problem is or how to work around it?
Thanks in advance,
Tom