Known Issues for Sybase Unwired WorkSpace – Device Application Development

In Windows7, if the generated project target path contains non-ASCII characters, the compilation fails. This issue occurs because the default character encoding of Windows 7 is INconsistent with Java default String encoding.

This issue occurs when the region control takes up only one column.

Workaround: Set the region's horizontal span to 2 in the Device Application Designer.

Events cannot be set on the object passed to the event binding service because a site associated with the object could not be located.

Workaround: Move the statement of change data binding format event handle to the constructor of the form.

private void InitializeComponent()
 {
.........
      System.Windows.Forms.Binding localobjectattribute12EditboxBinding=new
        System.Windows.Forms.Binding("Text", this.LocalObjectBindingSource, "Attribute12",
        true, System.Windows.Forms.DataSourceUpdateMode.Never);
     localobjectattribute12EditboxBinding.Format += new 
   System.Windows.Forms.ConvertEventHandler(Localobjectattribute12EditboxBinding_Format);
this.localobjectattribute12Editbox.DataBindings.Add(localobjectattribute12EditboxBinding);
........
 }

private void InitializeComponent()
 {
.........
      System.Windows.Forms.Binding localobjectattribute12EditboxBinding=new
        System.Windows.Forms.Binding("Text", this.LocalObjectBindingSource, "Attribute12",
        true, System.Windows.Forms.DataSourceUpdateMode.Never);
     // comment the below line
     // localobjectattribute12EditboxBinding.Format += new System.Windows.Forms.ConvertEventHandler(Localobjectattribute12EditboxBinding_Format);                       this.localobjectattribute12Editbox.DataBindings.Add(localobjectattribute12EditboxBinding);
........
 }

public FormUpdateLocalobject()
{
   Cursor.Current = Cursors.WaitCursor;
   InitializeComponent();
   if (this.localobjectattribute12Editbox.DataBindings != null && 
      this.localobjectattribute12Editbox.DataBindings.Count != 0)
         {
             this.localobjectattribute12Editbox.DataBindings[0].Format += new 
                System.Windows.Forms.ConvertEventHandler(Localobjectattribute12EditboxBinding_Format);
         }
............
}

As a result, you cannot scroll to the bottom of the table.

Workaround: Refresh the screen.

The type or namespace name 'Drawing' does not exist in the namespace 'Sybase.UnwiredPlatform.Windows'.

Workaround: Add C:\UnwiredPlatform\Unwired_WorkSpace\VisualStudio\ComponentLibrary\PocketPC\Sybase.UnwiredPlatform.Windows.dll to project reference before you add the Sybase controls through the form designer.

In the Device Application Designer, if the generated BlackBerry screens have input fields that expect a Datetime type, and if a device user then enters invalid Datetime values (for example, "2010-1111-01T1111"), no validation error dialog appears.

Workaround: Use the datetime picker to ensure the value is entered correctly.

When synchronizing a child MBO to submit a composite delete for a child MBO, an error message appears: com.sybase.up.bobclient.data.MobileAppException:com.sybase.persistence.OjbectNotFoundException. This error occurs because the parent has been deleted for that specific child, and therefore the operation cannot be successfully submitted.

Workaround: Do not synchronize the child MBO.

When you update or delete a pending new object, and configure the Device Application Designer to submit the operation immediately, you get an ObjectNotFoundException.

Workaround: Ensure all create, update, delete operations are configured identically, either with a pending state or not; do not mix them.

Workaround: If the device client database throws this exception in a JOIN query, verify join fields to ensure they are the same type.

This problem is restricted to the emulator, and does not occur in the device itself. The error is caused by the SQLite library, which handles applications installed on external storage memory differently than those installed in the main storage area.

Workaround: Install the application in the main storage memory of emulator, or test the application using an actual Windows Mobile device instead of the emulator.

If the BlackBerry device application (custom code or generated code from Device Application Designer) contains too many String literals, they are propagated into the generated Java classes. This propagation can cause compiling errors like Data contribution too large. Although RIM gives a suggestion at http://www.blackberry.com/knowledgecenterpublic/livelink.exe/fetch/2000/348583/800901/Support_-_Error_cod_data_section_too_large.html?nodeid=800816&vernum=0, the same error still occurs when the length of string literal exceeds 12315.

Workaround: Do not use long String literals.

Currently, for workflow form operations that list parameters generated by dragging and dropping, the child parameter mapping appears to not work and cannot be changed.

Workaround: Manually edit the generated .xml file.

Workaround: Select the list keys from the list control instead.

Tag Before Parameter: "
Tag After Parameter: " <jsmith@google.com>

Workaround: Use single quotes (' ') to tag parameters:

Tag Before Parameter: '
Tag After Parameter: ' <jsmith@google.com>

Workaround: Do not use this rule.

"The screen 'Department_create' has a menu item 'Create' which is trying to invoke the operation 'create' on the 'Department' MBO without having an instance of that MBO."

Resolve any of these issues and the error disappears.

If you have MBOs that are not bound to any data source, but have operations, create a "dummy" MBO so you can search for it within the workflow MBO search dialog.

If you have both an email starting point that invokes an object query and a menu item that triggers an object query on the same MBO, they each use different keys (for example, MyMBO and MyMBO_findAll_resultSetKey), regardless of whether the user needs to use the same key.

Workaround: Use the Flow Design page > Properties view > Matching Rules tab to remove these rules.

Workaround: Copy and paste only one Listview or Htmlview at a time.

You cannot send NULL values from the client to the server. If you attempt to retrieve NULL values from the server, the attempt fails.

Workaround: Do not use NULL values.