For your view to work, you have to identify what the key field(s) is/are. If it is this ID field you created that allows duplicates you could have real problems. When you do an update, the WHERE clause has something like WHERE ID = 3. So every record that has ID = 3 gets updated which means all these records now have those fields with the same data values. Now it is most likely you have multiple records will all identical data. What is the point of that? They only way you can successfully update and insert into a remote view is to have a truly unique way of identifying each record. It is OK to have an ID that can be duplicated so all records with a specific ID can be updated at the same time, but you still need one or more fields that uniquely identify each record. Otherwise, you have to do inserts yourself.

>To ALL;
>
>I've created a remote view to an access table. I've created an index in the table (id) and I allow duplicates on this index. In the update criteria, I have NOT forgotten to select the "Send SQL Updates" and I allow all the fields to be updated. I have "Set Multilocks ON" and the buffering status is set to 5. Through the browse and command window I and able to edit a record with issue BUT I an not able to add. The =tableupdate() command returns an array with the "-1" result.
>
>Through the form that I am using, I am not even able to edit the record never mind Add one on.
>
>Through this same connection I am able to update, add and delete records in the other tables. Other than field names, we have structured them the same.
>
>Any clues about where I should be looking for the problem??
>
>Thanks
>
>Sandy