Introduction
The DB2 Everyplace Sync Client API allows you to develop applications to handle bi-directional synchronization of relational data between a DB2 Everyplace Server and your hand-held device. The Sync Client API supports a wide variety of platforms including Palm, Pocket PC, Windows, Linux and more. It also supports many programming languages including C/C++, Java, and Microsoft Visual Studio .NET. The interface for the different languages is very similar. For more information about DB2 Everyplace, visit the DB2 Everyplace Website.
This tutorial is provided as a guide for developers who are new to the DB2 Everyplace Sync Client API and would like to build applications using this API. In this tutorial, we build a sample application and show you all the necessary steps to set up the build environment and explain the code used in this sample. The application will be written in C# .NET and the target platform is Pocket PC, but the concept covered here will be helpful in developing with other platforms or languages as well.
Sync Client application VNurse Client
In this tutorial, we will develop an application called VNurse Client. DB2 Everyplace provides an elegant solution in many scenarios where mobile workers need to access or modify information when they are not in the office. This sample is built upon the idea of a visiting nurse. One of the main responsibilities for our nurse is to visit patients and take their measurements, such as pulse rate or blood pressure, during her day. Instead of writing all the results on paper and re-entering all the data into the computer at the end of the day, she would carry a Pocket PC device. For each patient that she visits, she will take various measurements and record them using her mobile device, and when she gets back to her office she can synchronize all her data to the backend database with the click of a button.
DB2 Everyplace Sync Server comes with sample data of this VNurse scenario. It should be installed by default and set up properly if the Sync Server's installation was successful. Therefore, no extra steps are necessary on the server side.

