Unlinked Form/Sub_Form Synchronisation
- Thread starter gray
- Start date
spikepl
Eledittingent Beliped
- Local time
- Today, 18:31
- Joined
- Nov 3, 2010
- Messages
- 6,142
Ah so desu ka? 
So the OnCurrent on the subform got triggered by the cursor movement, and then immediately re-triggered by returning from fiddling with something on the parent form via code? And vice versa or something like that?
So the OnCurrent on the subform got triggered by the cursor movement, and then immediately re-triggered by returning from fiddling with something on the parent form via code? And vice versa or something like that?
The only explanation I can give is this.
The main purpose of a subform is to display related records of its parent form. When the bookmark of the parent record is changed unexpectedly it seems to get the subform to refresh (not requery) which will in turn fire the subform's On Current event in an attempt to ensure both forms are in synch. This happens regardless of whether the subform is linked to the parent. It also seems that the Current event of a subform is handled slightly differently when you click on the Record Selector/Nav buttons and when you click in a control. This is all speculation anyway.
The main purpose of a subform is to display related records of its parent form. When the bookmark of the parent record is changed unexpectedly it seems to get the subform to refresh (not requery) which will in turn fire the subform's On Current event in an attempt to ensure both forms are in synch. This happens regardless of whether the subform is linked to the parent. It also seems that the Current event of a subform is handled slightly differently when you click on the Record Selector/Nav buttons and when you click in a control. This is all speculation anyway.
