Syntax Errors When Creating a Database Mobile Business Object

Problem: Calls from Unwired WorkSpace to the EIS during MBO creation/development cannot distinguish syntax from data errors.

When adding an operation and corresponding SQL statement, Unwired WorkSpace executes the SQL statement to verify it is correct. Sometimes the return error is not a syntax error but a data error (for example, a foreign key restriction). The EIS API cannot distinguish syntax from data errors and exits the wizard.  

Be aware of the EIS schema to which you are binding the MBO. For example, verify that database data is correct, and enter the correct default values so the SQL statements execute correctly.

Related concepts
AutoCommit Option for JDBC MBOs Using an ASE Data Source
Passing an Empty String or Byte into a Required Binary Column in ASE
Related tasks
Binding an MBO to a Database Fails
Multilevel Insert Operation Fails
Attribute Length Set Incorrectly for Operation and Load Arguments
Unable to properly update the CDB because the partition was improperly assigned
Related reference
MBO Retrieves Incorrect Data
Relationship Error
Warning Message When Creating Relationships
Troubleshooting Default Values for Adaptive Server® Anywhere uniqueidentifiers
Preview Errors for a Web Service Mobile Business Object with date/time Types
Web Service Mobile Business Object Must Be Connected to Connection Profile
Refresh Fails Due to Missing Load Argument Default Values
Input Parameters Fail to Generate for Complex Data Sources
Output Mapping Warning Message for Multilevel Insert Operations
Sybase MBOs That Invalidate the Cache