Support Forum

You have two major methods how to save data in the database:

1. By using DB Execute command and writing your own INSERT and UPDATE statements. This method gives you the biggest freedom to manipulate data as you like it. Here you will need the If-Then-Else to decide which DB command to execute.

2. By using Save command to do this automatically. This second method only works if you used an option Create OriginalRowSet. Then, if you add or modify Row elements under RowSet, and execute Save command - MobileTogether will compare RowSet with OriginalRowSet and will produce INSERT, UPDATE, and DELETE statements automatically for you. There is no need for If-Then-Else in this case. Please take a look at the "Connecting Your Database to your Mobile Solution" video here http://www.altova.com/mobiletogether/demos.html - it is using the Save method to save new data.

Feel free to ask if something is still unclear.

What did you mean with the first question "how to do it in OnButtonPressed, which command I should use here?" - how to start editing or save data?

---

Altova MobileTogether Experts

IF we insert/edit something in third subpage (SEE THIRD_PAGE), and go back to second subpage (SECOND_PAGE) to show the result (DB2), how can we do it?
reload function in onButtonPressed in third subpage cant select DB2 in second subpage. That is mean we can't refresh the second subpage contents. Please help.
I put ADD and EDIT 2 button on third page, when user want add new REMARK, they should click ADD button, if they want edit existing REMARK, click EDIT button. I know we should not do this way, I do not know how to make ONE button <SAVE> to do it.

You need to add DB2 page source to the third sub page, then it will become available for reload.

We would love to help you, but it becomes increasingly difficult to understand what you are doing based just on your screenshots. Can you attach here your design file? Or send it to Altova Support if you don't want to make it public

do we need add OriginalRowSet for the DB3 WHICH IS FINAL TABLE TO BE INSERT/EDIT?

I've now read through your document. It would be a lot easier to answer you if you could attach (or send to Altova Support) your actual MTD file, but I will try based on your description and questions:

1. This is just a warning: your method for getting the sequence number by using MAX(remark_sequence) and adding 1 to it is dangerous. This is because if you have two drivers editing their records at the same time, they will get the very same sequence number

2. You are using "Go to Subpage event" command from your subpage. Without seeing your MTD file I can only guess that this was the actual error - you only need to Close Subpage, which will return you to your previous subpage, so try to remove the Go to Subpage.

3. - if you want to use the Save command, then yes

4. Save command uses Primary Key from your database to identify the record. I guess in your case SHIPMENT_GID is such a Primary Key. It then compares all other fields in a Row and OriginalRow with the same PrimaryKey. If any of the other fields changed - it will generate an UPDATE statements for those changed fields. If there is no OriginalRow with the same Primary Key - it will generate an INSERT statement

Now, if you have in $XML2 all fields from a DB3 Row, then you can implement the desired SAVE button instead of ADD/EDIT buttons this way:



What happens here - if it was an existing record, then you delete it from the RowSet first and it will be appended by the next Append Node command. If it is a new record, then you set new sequence number and append the node - the Delete Node will do nothing, because there is no existing record.

After all this Save will compare differences between RowSet and OriginalRowSet and propagate your changes to the database.

Important: you can do this trick with Delete Node/Append Node only if $XML2 contains all fields from $DB3 Row, otherwise you will lose some of the field values. If $XML2 does not have all the fields, then you need update every field in $DB3 Row instead of Delete/Append - let me know if I should help you to do this properly.

---

Altova MobileTogether Experts

Sure!

attached dmp file here which generated when crashed at insert new record. when save edit record, it did not crash, but not save the result.
I use following command at onButtonPressed for SAVE EDIT:

1. Update Node $DB3/DB/RowSet/Row[ @SHIPMENT_GID = $XML2/Row/@SHIPMENT_GID and @STOP_NUM = $XML2/Row/@STOP_NUM and @REMARK_QUAL_GID = $XML2/Row/@REMARK_QUAL_GID]
with Result of $XML2/Row/@REMARK_TEXT

2. Save $DB3(DB)

but it did not save.

This statement

Update Node $DB3/DB/RowSet/Row[ @SHIPMENT_GID = $XML2/Row/@SHIPMENT_GID and @STOP_NUM = $XML2/Row/@STOP_NUM and @REMARK_QUAL_GID = $XML2/Row/@REMARK_QUAL_GID]
with Result of $XML2/Row/@REMARK_TEXT

is not correct. If you don't want the combination of Delete and Append node as I suggested it to you, then you must modify your statement to update the @REMARK_TEXT in your Row and not the Row itself (add /@REMARK_TEXT on the end)

Update Node $DB3/DB/RowSet/Row[ @SHIPMENT_GID = $XML2/Row/@SHIPMENT_GID and @STOP_NUM = $XML2/Row/@STOP_NUM and @REMARK_QUAL_GID = $XML2/Row/@REMARK_QUAL_GID]/@REMARK_TEXT
with Result of $XML2/Row/@REMARK_TEXT

Thank you for the dump file. We have now found the reason for crash and fixed it for the next release.

For you in order to avoid crashes with your current release, open the actions in your Add button, remove Save action and insert a new one. The existing Save action was internally corrupt, and by inserting a new one everything should be fine.

Sorry for inconvenience!

the $DB3 is blank for insert function, since there is no any record at that moment for that select statement:
SELECT * FROM SHIPMENT_STOP_REMARK
WHERE SHIPMENT_GID = :Param_SHIPMENT_GID
AND STOP_NUM = :Param_STOP_NUM
AND REMARK_SEQUENCE = :Param_REMARK_SEQUENCE

with Param_SHIPMENT_GID set to $XML2/Row/@SHIPMENT_GID
Param_STOP_NUM set to $XML2/Row/@STOP_NUM
Param_REMARK_SEQUENCE set to $XML2/Row/@REMARK_SEQUENCE

That is why I original select whole table for DB3 which has thousand records, instead of select statement.
I know select whole table is slow down performance, just do not know if we can use select statement here.