List of Known Issues for Sybase Unwired WorkSpace Visual Studio Edition

If you have an MBO profile parameter in a situation where it does affect the results, the default setting for Filter By (unchecked) does not work. If you change the default setting for Filter By in other cases, the changed Filter By setting does not work.

Workaround: Do not change the default Filter By setting for an MBO parameter unless you have a profile parameter in a situation where different values of the parameter return different results.

If you generate Windows Mobile client code from Sybase Unwired WorkSpace Visual Studio or Eclipse Edition, and then open the generated solution in Visual Studio 2008, the Sybase Unwired Platform custom controls are not visible in the Form Designer's Toolbox. As a result, you cannot drag and drop them to create your own forms.

Workaround: Manually define the Sybase Unwired WorkSpace custom control instances, create the controls, and set their properties.

When you generate client code for the target platform Windows Mobile 6.0, if you get an error message saying, Cannot create the project. Generation canceled., it most likely means that you have not yet installed the Windows Mobile 6 SDK.

Workaround: Download the Windows Mobile 6 SDK (Classic or Professional ) from www.microsoft.com, install it, and try the code generation again.

When you generate client code including GUI from Sybase Unwired WorkSpace Visual Studio or Eclipse Edition, you cannot open the generated forms in Visual Studio Form Designer. This is a known bug of Visual Studio.

Workaround:

1. Go to the directory C:\Windows\Microsoft.NET\Framework\v2.0.50727.
2. Open the Microsoft.CompactFramework.Common.targets file.
3. Locate the tag: Name="PlatformVerificationTask">
4. Change it to: Name="PlatformVerificationTask" Condition="'$DoPlatformVerificationTask'=='true'">
5. Save the file.
6. Repeat the process with C:\Windows\Microsoft.NET\Framework\v3.5.
7. Restart Visual Studio 2008

This workaround disables the platform verification. If you want to enable it, you can define an environment variable DoPlatformVerificationTask and set its value to true.

When you use Sybase Unwired WorkSpace Visual Studio Edition, on top of Visual Studio non-English edition, generating client code is stopped with the exception, "The Visual Studio template is corrupted...."

Workaround:

1. Go to C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ProjectTemplates\CSharp and locate the Sybase Unwired WorkSpace folder.
2. Open the folder named 1033.
3. Copy the contents of this folder to the correct location for your version of Windows:
   
   • Windows XP - C:\Documents and Settings\<Current User>\My Documents\Visual Studio 2008\Templates\ProjectTemplates\Visual C#
   • Windows Vista - C:\Users\<Current User>\Documents\Visual Studio 2008\Templates\ProjectTemplates\Visual C#
4. Open Visual Studio 2008 Command Prompt from Start > Programs > Microsoft Visual Studio 2008 > Visual Studio Tools.
5. Select Start > All Programs > Microsoft Visual Studio 2008 > Visual Studio Tools > Visual Studio Command Prompt.
6. Execute this command:

   devenv /setup

If a WSDL contains multiple bindings, when you create a Create, Update, Delete, or Other operation using the MBO Operation creation wizard, the wizard fails to display operation parameters.

Workaround: Manually modify the WSDL file and leave only one binding, then the parameters will show properly in the MBO Operation creation wizard.

When developing MBOs, if a parameter or argument name exceeds the 100 character limitation, the following deployment error displays (on the runtime side):

Caused by: com.sybase.jdbc3.jdbc.SybSQLException: SQL Anywhere Error -638: Right truncation of string data.

Workaround: Limit parameter and argument names to 100 characters.

Although Sybase Unwired WorkSpace supports batch editing rows of table information (for example, parameter mapping and attribute mapping), SAP MBOs do not support this feature. When defining an SAP MBO, if you define default values for multiple rows, at runtime only the first row's value is set.

Workaround: To set default values, define them for each row individually, not by batch editing.

Sybase strongly recommends that you do not uncheck the Filter By checkbox on mobile business object (MBO) parameters for syncable MBOs.

Workaround: None.

When you export a mobile application project from Visual Studio to Eclipse, personalization keys used as data source credentials are not deployed to Unwired Server. Regular personalization keys used in MBO attributes and parameters are deployed correctly.

Workaround: Open the exported model in Eclipse and manually add the personalization keys.

Using DB2 as the back-end database, when synchronizing data, occasionally the connection fails with the message, com.sybase.djc.DataStoreException: Unable to close suitable (LRU) connection.

Workaround: None.

If an MBO is created from SQL 2005 stored procedure output parameters, when the MBO is deployed to the server, the data cannot be retrieved during synchronization.

Workaround: None.

If you use the Device Application Designer to create an application for Windows Mobile 5 Smartphone or Windows Mobile 6 Standard, some screens, such as ListDetail, do not display correctly on the device.

Workaround: Open the device project in Visual Studio and refine the layout there.

When an MBO or operation is defined using a stored procedure, if a parameter has the NUMBER datatype, the error Specified cast is not valid occurs. This error indicates that the stored procedure cannot be executed.

If a parameter has a CURSOR datatype, the error Unknown SQL Type-404 occurs.

Workaround: Use an Oracle native or OLE DB connection.

If you are using a SQL Anywhere or DB2 native connector and you create an MBO by dragging a stored procedure onto the mobile application diagram, the length of the scalar attribute is set to 10.

Workaround: You can manually change the attribute length in the Detailed Properties dialog, or use an OLE or ODBC connection instead of the native connection; both use the correct Scalar attribute length.

If you are using an ODBC connector and you drag an Oracle stored procedure onto an MBO, the generated SQL is incorrect.

Workaround: Use the Oracle native or OLE DB connector.

If you are using a SQL Anywhere native connection, you cannot drag a stored procedure onto the mobile application diagram to create an MBO.

Workaround: Access SQL Anywhere using an ODBC or other connection rather than the native connection. In most cases, you can open the Specify SQL Query page and generate SQL from a selection or define the SQL manually.

If you are using an ODBC or OLE connector with an Oracle database, navigating the procedure node is extremely slow.

Workaround: Use the Oracle native connector.

When using an ODBC or OLE connector with Oracle, the Mobile Business Object Creation wizard always loads all database tables, which seriously slows wizard performance.

Workaround: Use an Oracle native connector.

For Adaptive Server Enterprise and Oracle OLE DB connectors, it is not possible to get the primary key information for the table or the view and thus the WHERE clause cannot be constructed for generated SQL statements.

Workaround: Manually add the WHERE clause to the generated SQL statement.

When you define an MBO from a very large Adaptive Server Enterprise view, the creation wizard may not work and then reports an internal driver error from ODBC.

Workaround: The problem is due to a large view size. Downsize the view to have less data.

Occasionally, when creating or editing a complex MBO using SAP as the back-end database, performance can slow excessively. This may occur when you click Finish to create the MBO, or when you attempt to load an existing MBO that you want to edit.

Workaround: Close the Mobile Application Explorer, then restart Visual Studio.

If you browse to a property file to create an SAP connection rather than entering the properties yourself, each time you open the Mobile Business Object Creation wizard to create an SAP mobile business object, the BAPI metadata is reloaded from the SAP system, which can take awhile.

Workaround: If you use a named connection, data loads faster, but you must manually delete the serialization files if the metadata changes.

Serialization files are located in C:\Sybase\UnwiredPlatform-1_2\Unwired_WorkSpace\VisualStudio\toolingapi\sapCache.