When updating and reading forms, you can use any recono in your url by appending a /xx/ where xx i the recno when querying data. When you save your data you might do the same, but there might be consequences if other people (session in other web browsers or remote apps) are doing the same. Each server request on remote or web are always started by setting the query (searching up the data) without any regards to what the data was when the first query was done. This means that it there where inserted data by someone else between reading the data and updating the data, the record number you had when reading the data might not be the same as when you are saving the data.

Ex. you have one field with a name and when you start you have 2 names in your table (Ole and Dole). When you did the query you asked for all the records in acending order so the multiview will then be ['Name': 'Dole', 'Name' : 'Ole']. You ask for /1/ that gives you Ole. Then some one in between you read the record and pressed the save button add the name Doffen. Then your multview on your query when saving data will be ['Name' : 'Doffen', 'Name': 'Dole','Name' : 'Ole']. You ask to update /1/ so then you expect to save a the record with name Ole, but will overwrite Dole instead.

To avoid this, the best way is to always use /0/ when updating and using a query with an unique key to identify the correct record. 

DataEase will in most cases work when not using sorting as all records will then be added to the last record but if someone deletes a record with a lower record number between your read and update, you will have the same problem on unordered multiviews.