A recent mysterion. Users running Windows XP or Windows 7 Pro could run my Access 2010 split database perfectly, until the recent Office SP1 update. Now XP users are still ok, but Windows 7 Pro users experience a "Microsoft Access has stopped working" crash with one particular form (the other 40 or so forms run fine). The form that crashes has a continuous subform and two linked 'parallel' subforms (showing detail records related to the record selected in the continuous subform).
Perhaps there is a new sensitivity to the degree of cycling needed to put the ID of the selected record from the first subform into the main form to then link the second and third subforms to that ID? (Just a guess.)
Is anyone else seeing similar behaviour? Any ideas anyone?
Perhaps there is a new sensitivity to the degree of cycling needed to put the ID of the selected record from the first subform into the main form to then link the second and third subforms to that ID? (Just a guess.)
Is anyone else seeing similar behaviour? Any ideas anyone?