K
Kyle Burke
We are experiencing an issue when we close a recordset on
one bound form that corrupts the recordset of the calling
bound form's recordset. We are using Office XP with all
the latest service packs. Here's the details:
1. We have two bound forms Main and Policy. The forms are
bound to different tables in our Access Database. Main has
subforms that are linked to Main via a particular field.
The Policy form is NOT linked to Main and does not use any
of the same underlying data.
2. At the click of a button, the Main form opens the
Policy form. The code in the Main form that launches
Policy with the command:
DoCmd.Open "Policy"
3. The Policy form does some work and at the close of the
form we close the Recordset bound to the Policy form. In
testing the issue, the symptom still occurs even if we
bypass ALL of the logic in Policy, leaving only the
opening and closing of the Policy form itself.
4. As soon as we close of the Policy recordset, Main's
recordset becomes corrupted. Some of the name and value
fields of the recordset become invalid while other
properties are uneffected. For example, the recordset
retains its recordcount and all of the field names (in the
name property), but produces the error "undefined
function" when a reference is attempted to the value
property.
one bound form that corrupts the recordset of the calling
bound form's recordset. We are using Office XP with all
the latest service packs. Here's the details:
1. We have two bound forms Main and Policy. The forms are
bound to different tables in our Access Database. Main has
subforms that are linked to Main via a particular field.
The Policy form is NOT linked to Main and does not use any
of the same underlying data.
2. At the click of a button, the Main form opens the
Policy form. The code in the Main form that launches
Policy with the command:
DoCmd.Open "Policy"
3. The Policy form does some work and at the close of the
form we close the Recordset bound to the Policy form. In
testing the issue, the symptom still occurs even if we
bypass ALL of the logic in Policy, leaving only the
opening and closing of the Policy form itself.
4. As soon as we close of the Policy recordset, Main's
recordset becomes corrupted. Some of the name and value
fields of the recordset become invalid while other
properties are uneffected. For example, the recordset
retains its recordcount and all of the field names (in the
name property), but produces the error "undefined
function" when a reference is attempted to the value
property.