fix ACCESS error 3340

There is a problem with ACCESS that Microsoft is addressing. For now, I need someone to reprogram our queries as per suggestions given below Modify All Your Update Queries If you decide to modify your queries, you'll need to locate all the Update queries that trigger the error. These could be saved queries and SQL queries invoked in your code. Once you identify them, you'll need to modify them so they update the results of another query, rather than updating a table directly. These examples are provided by Microsoft in the referenced page above. For example, if you have this query which gets flagged as corrupt: UPDATE Table 1 SET [login to view URL] = "x" WHERE ([Table1].[Field2]=1); You can create a new query (Query1) defined as: SELECT * from Table1; And update your original query to: UPDATE Query1 SET [login to view URL] = "x" WHERE ([Query1].[Field2]=1); By replacing all references to Table1 with Query1 this will produce the same results and avoid the error. Not a Best Practice Needless to say, this is a brutal exercise that would need to be performed for every one of your databases, and retested before you deploy it again. It's also not considered a "Best Practice", so the effort does not produce a long term benefit. Total Access AnalyzerIf you have our Total Access Analyzer program, it documents your database queries and identifies which ones are Update queries, so that can help. It also identifies unused queries, so you may be able to delete some without the need to modify them. Replace Tables with Queries An alternative is to replace the affected tables with queries. For instance, you can rename "tblCustomer" to "tblCustomer_shadow", then create a query called "tblCustomer" that is query on the shadow table. SELECT * FROM [tblCustomer_shadow] With this, all the queries that reference tblCustomer, now reference the query. Since the Update query bug doesn't apply to queries that update queries, this eliminates the need to modify the individual queries. However, there's a limitation. Any code that tries to open the table fails if the table is now a query. This would include comments like: [login to view URL] Macros that open a table TableDef or TableDefs collection OpenRecordset commands with explicit table options