Apologies for the wall of text. Future edits will likely add screenshots and other visual elements.
Queries in Microsoft Access can be created by any one of four methods
Editing a record value from a query in datasheet view will result in a change in the underlying record value, assuming the query field is not an aggregation or concatenation of multiple sources of information.
Forms and Reports can be used to display information from queries in a form alternative to a simple "Datasheet" view which appears similar to an Excel-style spreadsheet. Forms are targeted to on-screen display, whereas Reports are targeted to those printed on paper.
In the example above, a reference field (SupID) can be used to indicate the ID of that employee's supervisor.
Using something as simple as a DLOOKUP can return the name of that supervisor.
eg. DLOOKUP("Name","EmployeeTable", "ID = " & SupID)
Another good example of this is to look at how automated Access switchboards are created, and more specifically the construct of the Switchboard table. Each switchboard option refers to another option within the same table - similar to how this example self references.
Be sure to remove other variables from the equation while testing
Network Corruption
Do not load the client off of a network. Put it on the local drive and run it from there.
Corporate Builds
If you are in a corporate environment that is using "computer builds" and have had no success with Decompiling, Testing Memory, nor stripping Binary data - then refuse to do further testing until the IT team can provide the user with a test machine that has only Windows, Office, and Service Packs installed.
All software and updates should be installed by hand without using unattended installs. Do not install antivirus on this machine for testing.
Understand that many IT departments simply try to do a One-Size-Fits-All approach with the builds, and their builds are all based on one another. Over time, software conflicts can directly cause Access to crash or act strange.
Bad Power
As mentioned in the memory example - power fluctuations can cause computer errors. If the database is in an industrial building, then try to get your hands on a power conditioner or a UPS that provides clean power (off the battery, not off the main passing through a Metal-oxide Varistor)
Also, check the power supply cable that is plugging into the power bar or outlet. Make sure that the gauge and voltage specs are sufficient. IT departments often leave power cables plugged in at the station and just remove the machine. After many years, they are using beefier power supplies, but haven't switched out the cable. It makes a difference. When in doubt, bring a new, thicker cable.