Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Mobile Client Companion Frequently Asked Questions

General questions

Framework

Upgrade Issues

Synchronization Issues

Synchronization Options

Deployment


As of which CRM version / service pack is the .NET version of SAP Mobile Client Companion (also known as PDA Companion) available?

With CRM 4.0 SP12 and CRM 5.0 SP07 the .NET version has been introduced. The former eVB (embedded Visual Basic) code line has been migrated into .NET, along with the introduction of additional improvements (e.g. new sync-layer).

back to top

What application versions of Mobile Client Companion are available?

Mobile Client Companion comes as a version for the Pharmaceutical and for the Consumer Goods industry.

back to top

What platforms are supported to run the .NET version of SAP Mobile Client Companion?

Pocket PC 2003 Second Edition and Windows Mobile 5.0 are supported. In order to run the .NET solution you also require the .NET Compact Framework (.NET CF 1.0 is required for 4.0 SP12 onwards and 5.0 SP07 and 5.0 SP08. And .NET CF 2.0 from 5.0 SP09 onwards).

back to top

What database versions are supported for Mobile Client Companion?

  • Microsoft SQL CE 2.0 (aka Microsoft SQL Server 2000 CE Edition)
    • For CRM 4.0 all SPs
    • For CRM 5.0 SP07 and SP08

  • Microsoft SQL CE 3.0 (aka Microsoft SQL Server 2005 Mobile Edition)
    • For CRM 5.0 SP09 and above

back to top

Are Views, Indexes and Joins supported?

No, Mobile Client Companion doesn't support the same.

back to top

I have done enhancements to the previous eVB version of Mobile Client Companion. How can I migrate those into the new .NET environment?

There is a code migration tool available that helps you to migrate your own eVB code into .NET. Make also sure you have considered the "Mobile Client 5.0 Post-migration Troubleshooting Guide" that can be found on the SAP Service Marketplace (Installation & Upgrade Guides for Mobile Sales Laptop).

back to top

What OSS Notes should I particularly consider to migrate and run the .NET version of SAP Mobile Client Companion?

For CRM 4.0 (In addition to the other Notes under Component CRM-MSA-PDA):

  • 951456 - Migration of SAP PDA Companion 4.0 to Visual Basic .Net
  • 1020387 - Prefill Entries for SAP Mobile Client Companion 4.0
  • 1010065 - Performance Improvement for PDA Companion
  • 1015799 - DotNetPDAGenerator HotFix For 40SP12
  • 1010572 - Fixes for Marketing Attributes MobileClient Companion 40SP12
  • 1018975 - Activity Filter for Synchronization not Working 4.0 SP12
  • 1017833 - Signature Capture in Mobile Client Companion
  • 1017603 - Mobile client Companion Upgrade Units 4.0 SP12

For CRM 5.0 (In addition to the other Notes under Component CRM-MSA-PDA):

  • 993742 - Hot Fixes for MobileClient Companion 5.0 SP07
  • 989495 - Prefill Entries for SAP Mobile Client Companion 5.0
  • 989496 - Generated Application CAB Files for Mobile Client Companion
  • 1027257 - PDAApplication Migration fails - Corrupt templates folder
  • 1012639 - Fixes to templates for DotNet PDAGenerator
  • 1016394 - Hot Fixes for MobileClient Companion 5.0 SP08

back to top


Supporting Mobile Client Companion with WM 2005 and WM 2003 SE devices

Problem description

The existing eVB based CRM Mobile Client companion has issues functioning on WM 2005 and WM 2003 SE devices.

Reason

Microsoft has stopped supporting eVB on these devices. The new framework is the .NET CF framework.

Solution

Apply note 951456 to upgrade the eVB based applications to .NET CF. The upgrade guide available in the Service Market Place for this note contains the required steps for upgrading to .NET

back to top

Combo dropdown Event Handler

Problem description

The eVB based framework did not support Combo_dropdown event-handler.

Reason

This was a generated event-handler in the eVB framework for handling hierarchy combos. Hence this could not be provided for user-handling

Solution

In the .NET framework, the hierarchies are handled in a different manner. Hence, we have provided the event-handler combo_GotFocus event has been provided that can handle the same function as combo_dropdown of eVB.

back to top

Global variables

Problem description

The eVB based framework did not support Global variables.

Reason

This was not planned as part of the eVB framework.

Solution

This is now supported with the new framework. To add global variables, Application free-script should be used for declaring. This would get generated as PDAGlobals.vb in the new application.

back to top

Problem description

HyperlinkClicked event-handler was not available in the eVB framework.

Reason

This was a framework limitation of eVB.

Solution

This has been included in the .NET framework.

back to top

Problems in Viewing Time Controls in Device

Problem description

In case of certain devices, the time control may display single digits in the hour, minutes and seconds fields.

Reason

This is caused by certain fonts not being available in the devices.

Solution

Apply note 956688 to solve this issue.

back to top

DateTime OnValueChanged Event Handler

Problem description

The eVB based framework did not support DateTime OnValueChanged event-handler.

Reason

This was a framework limitation of eVB.

Solution

This has been included in the .NET framework.

back to top

Form_OnUninitialize Event Handler

Problem description

The eVB based framework did not support Form_OnUninitialize event-handler.

Reason

This was a framework limitation of eVB.

Solution

This has been included in the .NET framework.

back to top

In the PDA, when the GUID is getting generated - is it in Upper Case?

Problem description

In eVB, the GUID generation took place in lower case which was causing issues, as the laptop is handling GUIDs in upper case.

Reason

This was a limitation of eVB version.

Solution

The GUID generation is now upper case.

back to top

What is not supported?

There are certain requirements that are not supported as yet with the .NET framework. The following table lists these changes and their availability.

Requirement

Availablility timelines

Reason

Options page label_click events

NO

This is a generated form, and cannot be provided for coding

Form _BeforeNew eventhandler

Not available

 

Further filtering in list tiles

NO

This is a framework class, and should not be changed

DetailManager - initCombo handling for special cases

NO

This is a framework class, and should not be changed

back to top


Code Migration - Generation fails

Problem description

Generation step fails during Code Migration

Reason

The generator involved during Code Migration would generate the eVB based PDA applications in VB6 class file format and compiles this. The above error could arise if the application generated is not in a compilable state. Reasons could be:
a. Uncompilable code
b. Incompletely defined hyperlinks

Solution

Check the log file that gets generated in the path CMT\Logs\ . This would provide information on why the generation failed. Make the corrections in MAS, and release the changelist before running CMT again.

back to top

Code Migration - Migration Fails

Problem description

Migration fails while running CMT

Reason

Third party dlls are not registered

Solution

Register all third party dlls (Typical eg: "adocedt30.dll" - the dll corresponding to Microsoft CE ADO control.
To be registered in the corresponding path C:\Program Files\wce300\Pocket PC 2002\desktop\dataaccess\adocedt30.dll)

back to top

Migration code written outside MAS

Problem description

eVB code written outside MAS to handle certain events not supported in the eVB based framework needs to be migrated to .NET CF.

Reason

There might some code written outside MAS, as no support from the existing eVB PDA application framework was available for certain event-handlers. This also needs to get migrated to .NET.

Solution

Before running CMT, please put the required code as Methods into the respective tiles in MAS. Then run CMT. This would ensure that the code is migrated to .NET also. After CMT, run MAR Upgrade and MDW Upgrade, and then you could use the new event-handlers supported for .NET framework to call these methods.
Some examples of these changes are :
a. Language based label handling - These can be added using the translation tool.
b. Buttons need to be created using MAS only.
c. Scripting of hyperlink click events
d. Combo dropdown
e. Global variables

back to top

MAR Upgrade - Collisions on wrong branches

Problem description

While resolving collisions after MAR Upgrade, the collisions is shown between the branches of customer eVB code version and SAP migrated code version.

Reason

This occurs if MAR Upgrade was run on the ARS without releasing the changelist of CMT.

Solution

Restore the backed up ARS after CMT. Release the changelist and run MAR Upgrade again.

back to top

Compilation errors after migration and upgrade

Problem description

Compilation errors arise in the application code after migration to .NET

Reason

Certain changes for .NET cannot be taken care of by the Code Migration Tool. These changes have to be taken up manually.

Solution

Please refer to the upgrade guide, section "Post Migration Steps" for further information.

back to top


PDA synchronization component does not connect to SQL Server

Problem description

In some cases, the synchronization might fail, with reasons saving "cannot connect to SQL server".

Reason

This is because the security settings or firewall settings on the laptop might stop the device from connecting. Or the SQL Server might not be running on that server.

Solution

If SQL server is not running, please start SQL server.
If firewall settings are causing the problem, please make the required setting changes to let the connection go through.
If everything fails, please refer to http://support.microsoft.com/kb/814372/.

back to top

Synchronization to PDA fails

Problem description

The synchronization of data to PDA fails with a window saying nullreferenceexception for SAPPDASync.

Reason

Some other application might be accessing the database at the same time. SQL CE supports only one access to a database at a time.

Solution

Close the other application accessing the database, and sync again.

back to top

Missing Companion Object on re-installation of MS ActiveSync

Problem description

The companion object might be lost after re-installation of ActiveSync

Reason

This happens because the registry gets rewritten when Active Sync is installed again.

Solution

Please apply note 954626.

back to top


What synchronization Options can be changed?

Click on the Config button on the sync module to view options.

Polling Interval
User can change the server polling interval by entering values in the Timeout interval. This value is used by the sync mechanism to connect periodically to the Ides DB.

Packet Size
This is the number of messages processed by the sync module in one go. This should be optimally entered as per the DB load. Users can change this value in the packet size field provided in the config screen.

Compact SqlCe DB
The SqlCe DB sometimes occupies more space than it actually should. The user can select this option to compact the DB. This should be done frequently and it will free considerable amount of bytes in the pocket pc.

back to top


Does Active Sync check if the application to be installed is currently running on the device?

Active Sync detects the existing application and uninstalls it before installing the newer version.

back to top