Troubleshooting Database Mobile Business Object Errors

Problem: If a database MBO is created from an ASE stored procedure that uses chained transaction mode, it may fail (does not display table data) once deployed and executed because the runtime server executes in autocommit mode.

During MBO development, by default, preview of a database MBO uses SQL in chained transaction mode, so any changes made to the datasource are rolled-back to avoid permanently changing data. The result is the MBO behaves as expected when previewed, but fails when a device application attempts to synchronize the MBO, and an error is logged in Unwired Server's uep.log file.

Solution: If you see chained transaction mode related errors in the uep.log file, run sp_procxmode procname, anymode, where procname is the name of the stored procedure, so the stored procedure runs in autocommit mode.