List of Known Issues for Device Applications

On the Windows Mobile platform, a FormatException could be thrown by the client API if the non-string attribute contains no data. This is caused by the generated code's attempt to convert an empty string to a type of non-string.

Workaround: The client program can use a catch clause to properly catch the FormatException and proceed. The value of the corresponding attribute can be assumed to be whatever the type's default initialized value should be.

When there are more than 30 syncable MBOs in a package and less than 30 syncable MBOs in a Device Application Designer file, after generating the code for the device application, a SQLE_TOO_MANY_PUBLICATIONS error occurs when synchronizing the MBOs on Windows Mobile.

Workaround:

1. Before synchronizing MBOs, open the Program.cs file, which is located in the folder of the generated project in %Visual Studio solution folder%\%Client project name%.
2. Set Sybase.UnwiredPlatform.Data.DatabaseUtilities.UseDynamicPublication = true.

A child MBO can only display correct detail information for the first 25 records.

Workaround: Use Search screen or Sort function to filter the data so that it appears in the first 25 records, or view data directly in the table.

The milliseconds portion of datetime data is not processed correctly. To cause datetime synchronization data to match server data, pass milliseconds as zero and check ShowMilliseconds.

Workaround: Ensure ShowMilliseconds is checked when you are programmatically passing a datetime value of zero with zero milliseconds as a synchronization parameter.

If you use SQL Anywhere or Adaptive Server Enterprise smalldatetime, datetime, timestamp, and time column types as MBO attributes, then UPDATE operations may fail because of the WHERE clause that is included for a concurrency control check in the generated SQL. Also, the CREATE operation may not return the same precision as inserted. This is because milliseconds and seconds are ignored for these column types.

Workaround: After creating the MBO in Sybase Unwired WorkSpace Eclipse or Visual Studio Edition, manually remove the fields of these types from the WHERE clause (used for concurrency control check) in the generated SQL query of the UPDATE operation. For the CREATE operation, do not enter seconds or milliseconds.

Because Windows Mobile 6 Standard Edition does not have a touch screen, the context menu is not accessible on this platform.

Workaround: None.

When you deploy a Sybase Unwired Platform application to a device and select the option to store the application on a memory card, the application cannot be launched automatically and causes an error.

Workaround: Launch the device application manually.

If you make a change to the child MBO on the server side, the screens for the parent MBO are refreshed, but the screen for the child MBO that changed is not refreshed.

For example, if you have a Customer to Sales order relationship and make a change to Sales order on the server side, all screens for the Customer MBO are refreshed. but screens for the child relationship with Sales order are not.

Workaround: Go back to the Customer screen and perform the relationship again.

On Blackberry devices, the Show Millisecond on Time Selection option in the Device properties does not work on a datatype column on the device application with a create and update operation, because of the behavior of the JDBC driver.

Workaround: If possible, set milliseconds to zero for time data on the server side before passing to an application on a Blackberry device.

On Windows Mobile devices, the application crashes if you open the Sort menu, then select the column name that represents a binary datatype column from the MBO.

Workaround: Remove the name of binary datatype column from the Sort menu.

Images that are larger than 500 KB do not display when deployed to Windows Mobile devices. Images that are larger than 12 MB cannot be deployed at all and an error message is displayed on the Unwired WorkSpace Console.

Workaround: Reduce larger images by scaling down the image or breaking the image into several smaller parts.

On Windows Mobile devices and emulator, after you have run the FILE MBO application once, on subsequent attempts to run this application it generates a SQLE_FILE_IN_USE error message and you cannot enter the application.

Workaround

On an emulator:

1. Perform a soft reset on the emulator.
2. Uncradle the emulator from the Device Emulator Manager.
3. Cradle the emulator from the Device Emulator Manager

On a physical device:

1. Perform a reset on the device.
2. Make sure internet access is successful.

On Windows Mobile devices, actions appear in the update log before the user synchronizes the device application. On other platforms, actions do not appear in the update log until the user synchronizes and submits the action screen.

Workaround: Perform a synchronization before checking the update log.