I am using the same general code I have used successfully in the past.The latest database is being copied to the user's local computer.

For example, employees can be associated with orders for which they are responsible by creating a table relationship between the Employee ID fields in the Employees and the Orders tables. Employee ID appears in both tables — as a primary key ... There are several reasons why you should create table relationships before you create other database objects, such as forms, queries and reports.

When you design a database, you divide your information into many subject-based tables to minimize data redundancy.

Web databases do not support the Relationships window.

You use Lookup fields to create relationships in a web database.

It's as if the application has taken a snapshot of the data and refuses to update it's view.

Oddly enough, I can update linked tables via SQL statements from the app.

You then provide Access with the means by which to bring the divided information back together — you do this by placing common fields in tables that are related.

To do this step correctly, however, you must first understand the relationships between your tables, and then specify these relationships in your database.

For example, the form shown here includes information drawn from several tables: 1. A table relationship works by matching data in key fields — often a field with the same name in both tables. Top of Page You can create table relationships explicitly by using the Relationships window, or by dragging a field from the Field List pane.