I have a bit of an odd situation here. The short short version: the database works fine for me after I added new features, but the client says reports are popping up with error 3089. Since I cannot duplicate this error or visit the site to see their computers, this will be tricky.
I do believe it has to do with the code I added to open the reports; they use a temporary table to hold some data for the queries underlaying the report. I use a very, very simple delete query to clean out the temporary tables, and then I add rows based on user input before opening the report which is filtered based on those rows.
So how could something as simple as:
go wrong? Is this some sort of security/permissions issue? And if so, what can I do to change it?
I'm using Microsoft Access 2003 with a Medium macro security setting. She stated that she is also using 2003.
I do believe it has to do with the code I added to open the reports; they use a temporary table to hold some data for the queries underlaying the report. I use a very, very simple delete query to clean out the temporary tables, and then I add rows based on user input before opening the report which is filtered based on those rows.
So how could something as simple as:
Code:
CurrentDb.Execute "delete * from FilterTable;"I'm using Microsoft Access 2003 with a Medium macro security setting. She stated that she is also using 2003.
