Troubleshooting Mobile Business Object Errors

Review these Mobile Business Object issues.

• Troubleshooting Mobile Business Object Operation Datatype Mappings
  Problem: When creating an operation for a mobile business object from the Mobile Application Diagram, parameter datatypes (int, decimal, image, and so on) are mapped to strings.
• Troubleshooting Previewing of a Database Mobile Business Object
  Problem: When previewing a database mobile business object using SQL, the connection is set to chained mode so it can rollback the query after preview. For ASE stored procedures, you may get an error similar to: Execution failed: Stored procedure 'pubs2.dbo.byroyalty' may be run only in unchained transaction mode. The 'SET CHAINED OFF' command will cause the current session to use unchained transaction
• Troubleshooting Redeployment of a Syncable Mobile Business Object
  Problem: After changing a mobile business object's syncable status, redeploying the mobile business object using Update does not update the syncable status of the deployed mobile business object.
• Troubleshooting Mobile Business Object Attributes
  Problem: Creating a Mobile Business Object with an index as an attribute name generates an error message.
• Troubleshooting Database Mobile Business Object Errors
  Describes database mobile business object (MBO) related errors and solutions.
• Troubleshooting Web Service Mobile Business Object Errors
  Describes Web Service mobile business object (MBO) related errors and solutions.
• Troubleshooting Binding a Mobile Business Object to a Database
  Problem: Binding a mobile business object (MBO) to a database, other than a Sybase database, fails.
• Troubleshooting File Mobile Business Object Errors
  Problem: After deploying a file mobile business object (MBO) that contains only an upload operation to Unwired Server, device applications are unable to successfully access them.

---

Created September 17, 2009. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com