# 4906 Updating Published Tables Using Sensitive Query Result Sets Can Cause Access Violation

---

I have an example that loads a query into a FireDac memory table, touches the FD table, and then walks back through and applys the updates to the underlying EDB tables. An AV will appear when you post against the original EDB query.

I can prevent the AV by either unpublishing the CodeSale table, OR by using a separate EDB query or table to apply the updates.