We are having difficulties in choosing the better approach, a client side or a server side updating of data?

Using MM Business Form's This.Save()

Using MM Business Form, we can use the this.Save() to save data in the server. The idea is to make sure that everything needed to be saved are already available regardless of the number of tables. Some tables concurrency setting are disabled because it's not smart to regularly popping up the users everything a record to be updated have a new value in the database when this.Save() is executed.

This setup I think is good if there are only few users simultaneously using the system and modules. But in an enterprise setting with hundreds of users, I have reservations if this methodology of updating data is correct because new data optimistacally overwrites data in the server.

Using Dynamic SQL

Using a dynamic SQL, I want to update data and I leave it to the database server the implementation of record locking and queuing of sql sent from application clients. The SQL statements are located in a separate class wherein the "inserts, update, delete" are generated dynamically. Once the SQL statements are completed, it will be sent to data server using this.execscalar() with transaction commit and rollback implemented.

In effect, this approach is a server side update as opposed to this.save() which is client side.

In your technical opinion, which approach is better?