This is a good one. If you ever see it don't expect the displayed message to be of any help what so ever.
I had a form with two sub forms. The Parent and both Children each had link fields called "Task_ID". Task_ID was used on subform properties Parent and Child.
I also had a Command Button to open a report in Print Preview using DoCmd from the on click property.
The report's data source was an imbedded SQL statement that grabbed and filtered on the value of the Parent's Task_ID field.
When the Print Preview Command button was Clicked it would either show the record or lock the application (randomly).
The unhelpfull 2486 Error Message would appear telling me that it couldn't do anything because code was still running.
My initial response and after mucho debugging deterimed that nothing was running!
Only after trial an error did it occur to me that maybe.....
Since there were multiple references to "Task_ID" on the form I renamed the Parent Control Name and the darned error was solved.
It didn't matter that the Print Preview was called from the Parent, nor that the subform's object names were not the same. Access simply got lost - fell down and couldn't get up!
Thank You Microsoft for your ever unhelpful error messages! <Growl !>
Bottom line - if you see this error look to any objects that might have the same names.
I had a form with two sub forms. The Parent and both Children each had link fields called "Task_ID". Task_ID was used on subform properties Parent and Child.
I also had a Command Button to open a report in Print Preview using DoCmd from the on click property.
The report's data source was an imbedded SQL statement that grabbed and filtered on the value of the Parent's Task_ID field.
When the Print Preview Command button was Clicked it would either show the record or lock the application (randomly).
The unhelpfull 2486 Error Message would appear telling me that it couldn't do anything because code was still running.
My initial response and after mucho debugging deterimed that nothing was running!
Only after trial an error did it occur to me that maybe.....
Since there were multiple references to "Task_ID" on the form I renamed the Parent Control Name and the darned error was solved.
It didn't matter that the Print Preview was called from the Parent, nor that the subform's object names were not the same. Access simply got lost - fell down and couldn't get up!
Thank You Microsoft for your ever unhelpful error messages! <Growl !>
Bottom line - if you see this error look to any objects that might have the same names.
