M-Business version-specific on-device code files

If you are using M-Business Client version 5.7 or earlier, you should use the PODS versions that came with that version of the client. This applies to the files listed below.

Table 1. M-Business version-specific on-device code files

Functionality	File name on Microsoft OSes	File name on Palm OS
On-device XML data	dbpod_quad.dll	dbpod_quad.prc
Date/Time Picker	mimedtpicker.dll	mimedtpicker.prc
List Viewer	mimelist.dll	mimelist.prc

The versions of these files that ship with M-Business Server version 6.5 and later do not work with M-Business Client version 6.2 and earlier. Beginning with M-Business Server version 6.5, the version numbers of the shipping PODS are synchronized with the M-Business Server version number. If you use any of these PODS in your applications, note the following compatibility requirements and make sure that none of your users with M-Business Client version 6.2 and earlier inadvertently get PODS from M-Business Server version 6.5 or later, unless you first upgrade them to M-Business Client version 6.5 or later.

Table 2. M-Business Server version and shipping PODS version

M-Business Client version	Required M-Business PODS version
6.2 or earlier	2.0.x
6.5 or later	2.1.x

M-Business Server version 6.5 and later bundles the 2.1.x version of the PODS. If your M-Business solution is deployed exclusively on 6.5 and later versions of M-Business Client, simply proceed as directed in the Upgrading and Installing M-Business Server.

If your solution is deployed on both 6.5 and earlier versions of M-Business Client, use the AG_CLIENTVERSION macro to vend the correct PODS version to each M-Business Client version. If you support some devices running Palm OS and other devices running Microsoft OSes, use the AG_DEVICEOS macro in your logic to vend the correct PODS version for the platform. See Using server URL macros to customize content for details regarding URL macros.

If your solution uses custom PODS, there is a compatibility issue only if the PODS make use of the getCharsetEncoding() or rebuildSelectionList() methods. PODS that utilize either of these methods must be recompiled with new header files to work on M-Business Client version 6.5 and later. The new header files are supplied in the pods.zip file. For instructions on downloading this file see Downloading and working with the PODS sample files.

Table 3. Compatibility of custom PODS and M-Business Client versions

M-Business Client version	Custom POD without affected methods	Custom POD with affected methods
6.2 or earlier	Use existing POD	Use existing POD
6.5 – 7.0	Use existing POD	Recompile POD with new header files

To determine whether your custom PODS need to be recompiled for the current version of M-Business Client, see Determining version compatibility with custom PODS and M-Business Client.

Send feedback about this page using email.