SQL Statement Yields Unexpected Results

Problem: A SQL statement yields unexpected results in runtime.

Explanation: This may happen when you use a non-Sybase database, and include a comparison operator in a definition SQL statement followed by a parameter; for example: "select * from ... where columnA=:parameterA, and the default value of this parameter is set to null.

Solution: If you need null as the default value, define an object or operation and manually write the definition SQL statement (for example, " columnA is null") in the Property view.

Related tasks
No Data or Images Appear on the Device
Binding an MBO to a Database Fails
Structure MBOs Not Automatically Generated After Rebinding
Multilevel Insert Operation Fails
Related reference
Troubleshooting MBOs
Troubleshooting Improperly Designed Mobile Business Objects
Database MBO Fails on Execution
Web Service MBO Sync Exceptions After an Interface Change
Search Errors and the RTRIM Function
Update Operation Fails
Relationship Error
Warning Message When Creating Relationships
Synchronization Fails if Binary Attributes Have Unspecified Length