Problem: A database mobile business object (MBO) that worked during preview, fails (does not display table data) when it is deployed and executed.
Explanation: This may happen if a database MBO created from an Adaptive Server® Enterprise stored procedure uses chained transaction mode. By default, MBO development preview uses SQL in chained transaction mode, so any changes made to the data source 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. An error is logged in the Unwired Server<hostname>-server.log file.
Solution: Check the <hostname>-server.log file for errors related to chained transaction mode. If you see them, use Sybase Unwired WorkSpace to execute a SQL statement that contains sp_procxmode <procname>, anymode, where <procname> is the name of the stored procedure, so the stored procedure runs in autocommit mode.