A new bug with MS Access has surfaced with the latest build (9029.2167) in which SQL Statements used to define a Record Source or Row Source (in forms/reports, combo boxes, listboxes, …) do not get saved after being modified and the user purposely saving the changes. They just don’t get committed.
There are a couple threads that have popped up relating to this issue, such as:
The Workaround
The proposed workaround directly from Microsoft is
A fix will be coming, in the meantime we have 3 workarounds:
- Close the builder without saving, then answer Yes when asked if you want to save
- Save the SQL statement as a query, then update the property to use the saved query
- Copy the SQL from the builder and paste it into the property sheet
Further Consideration
Build 9029.2167 appears to have several bugs and that some consideration should be given to disabling Automatic Updates and reverting your build to a prior version if you already have 9029.2167 installed until which time Microsoft cleans up this latest mess so you can reactivate it.
Over the years I’ve learned to use saved queries for Row and Record Sources. I’ve often seen Access truncate the SQL for no apparent reason.