Home    Products    Support  Downloads    Agents  Contact    About    Search

InControl Sync Pocket Access Database Transfer Utility

DOWNLOAD DEMO || DOWNLOAD TEST APP CODE (VB 6) ||

COST: $99.00 USD
COST: $199.00 USD (with source code)

Last updated: 31 August 2007

Benefits at a glance:

» Does not trigger the ActiveSync program, all file transfer is done silently
» Gives you the ability to syncronise a desktop database and a handheld database with one button click
» Reduced development time for your data driven software products, (will save you weeks !)
» Much reduced development costs for you and your company
» One click sync for your software users
» No messy ActiveSync setup for your users
» easy to use .DLL interface...
» One function call to export from MDB to CDB
» One function call to export from CDB to MDB
» Use the database drivers of your choice by providing the .DLL with a connection string
» As you are calling the .DLL you can name it what ever you like and place it where ever you like.
» At least twice as fast as ActiveSync for database transfer in both directions.
» You are not limited to syncronising your database to the My Documents directory on the handheld device

[TOP]

How it works:

The desktop .DLL carries out all the functions necessary to transfer a .MDB database from the desktop computer to the handheld .CDB PocketPC device without any interference by the ActiveSync software... and vice-versa. This is done by having the .DLL on the desktop which extracts data from and creates databases on the desktop. There is also an application on the handheld which the .DLL controls to carry out the same functions on the handheld device, all you have to do is give the .DLL the information it requires and it will do the rest !

As the .DLL can be declared in any programming language, and the path to that .DLL included in the declare statement, the .DLL file can be installed to anywhere in the desktop computer.
When calling the .DLL in your software you are able to provide a connection string for the connection to your database. With the connection string you are not limited to any one database format or driver set... if you do not provide a connection string, the microsoft ole.db drivers are used and a Access 2000 database is created / read..

The .DLL is called from within your own software product, you have one function call to transfer the database to the handheld device and one function call to transfer the database from the handheld device to the desktop computer. Within this function call you are able to provide:
      the path of the .CDB
      the path of the .MDB
      a connection string to the database drivers of your choice
      the title of the form shown on the handheld app
      your company name for display on the handheld app
      your company contact details for display on the handheld app

EXPORT FROM DESKTOP PROGRAM FLOW:
     .DLL converts .MDB to to special FTI file format -> .DLL tranfers FTI file to handheld device
     .DLL triggers handheld app -> handheld app converts special FTI file format to .CDB

IMPORT FROM HANDHELD DEVICE PROGRAM FLOW:
     .DLL triggers handheld app -> handheld app converts .CDB to special FTI file format
     .DLL tranfers FTI file to desktop -> .DLL converts special FTI file format to .MDB

All error reporting is via generated text files that can be read by your application...
     Both the desktop and the handheld device generate a detailed results.fti file that describes success or errors with a list of error descriptions.

As the file transfer between the desktop and the device is in the form of a text based file, no non-printable characters can be transferred.

With your company information shown within the handheld app's screen display, the software will fit into your own software very well.
During the install of your database driven software, you install the .DLL onto the desktop computer and the CESync.vb and CESync.exe onto the handheld device, supplied are handheld app's for SH x, ARM & Mips PocketPC processor architectures.

[TOP]

Example Function Calls (VB 6.0):

-=- Export -=-

Private Declare Function TransferDBToHandHeldEx Lib "P2PDll" (

ByVal CEAppPath As String, _ ByVal CECDBPath As String, _ ByVal ConnectionString As String, _ ByVal MDBPath As String, _ ByVal Company As String, _ ByVal Contact As String, _ ByVal AppTitle As String, _ ByVal ShowForm As Boolean) As Integer

TransferDBToHandHeldEx

"\program files\cesync\", _ "\program files\cesync\db.cdb", _ "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\program files\Fairport\knowledge.mdb", _ "c:\program files\Fairport\knowledge.mdb", _ "Fairport Technologies", _ "w w w . f a i r p o r t . c o m . a u ", _ "InControl Sync Utiltity", True

This function call will carry out the entire sync process RELIABLY by reading the database on the desktop. A special generated FTI file format on the desktop is then passed to the handheld device and then the application on the handheld device is triggered which will create the .CDB database on the device.

[TOP]

-=- Import -=-

Private Declare Function TransferHandHeldToDBEx Lib "P2PDll" (

ByVal CEAppPath As String, _ ByVal CECDBPath As String, _ ByVal ConnectionString As String, _ ByVal MDBPath As String, _ ByVal Company As String, _ ByVal Contact As String, _ ByVal AppTitle As String, _ ByVal ShowForm As Boolean) As Integer

TransferHandHeldToDBEx

"\program files\cesync\", _ "\program files\cesync\db.cdb", _ "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\program files\Fairport\knowledge.mdb", _ "c:\program files\Fairport\knowledge.mdb", _ "Fairport Technologies", _ "w w w . f a i r p o r t . c o m . a u ", _ "InControl Sync Utiltity", True

This function call will carry out the entire sync process RELIABLY by triggering the handheld app which reads the .CDB database and creates a special FTI file format on the handheld device. This file is then passed to the desktop and the mdb is created. If a connection string is not provided to the .DLL then an Access 2000 database is created on the desktop by default.

[TOP]

-=- CreateMDBFromFTI -=-

Private Declare Function CreateMDBFromFTI Lib "CESync" (

ByVal ConnectionString As _ String, ByVal MDBPath As _ String, ByVal FTIFilePath As String) As Integer

CreateMDBFromFTI

"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\program files\knowledge.mdb", _ "c:\program files\knowledge.mdb", _ "c:\temp\"

-=- CreateFTIFromMDB -=-

Private Declare Function CreateFTIFromMDB Lib "CESync" (

ByVal ConnectionString As String, _ ByVal MDBPath As String, _ ByVal CDBFileName As String, _ ByVal FTIFilePath As String) As Integer

CreateFTIFromMDB

"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\program files\knowledge.mdb", _ "c:\program files\knowledge.mdb", _ "\Program Files\CESync\MyDB.cdb", _ "C:\temp\"

-=- Copy Functions -=-

Private Declare Function CopyToHandHeld Lib "CESync" (

ByVal SourceFile As _ String, ByVal DestFile As String) As Integer

CopyToHandHeld "c:\program files\Fairport\MyFile.fti", "\program files\Fairport\MyFile.fti"

Private Declare Function CopyFromHandHeld Lib "CESync" (

ByVal SourceFile As _ String, ByVal DestFile As String) As Integer

CopyFromHandHeld "\program files\Fairport\MyFile.fti", "c:\program files\Fairport\MyFile.fti"

These functions should be fairly self explanatory. Use these functions to copy the export.fti file to and from the handheld device. You can also use these function for any other file transfer that you may need, such as the results.fti that is generated by the handheld CESync.vb app on the handheld device.

[TOP]

-=- Does DB Exist Function -=-

Private Declare Function DoesDBExistOnHandheld Lib "CESync" (

ByVal CEAppPath As String, _ ByVal CECDBPath As String) As Boolean

If DoesDBExistOnHandheld Then ...

This function allows you to check whether a partcicular file exists on the handheld device. For example you could check wether the CESync software is available on the handheld device... this would also suggest that you have an active connection to the handheld device.

[TOP]

-=-EXPORTING DATA FROM HANDHELD-=-

-=-IMPORTING DATA TO HANDHELD-=-

Handheld application allows users to see the progress of the database transfer.
Company, contact and form Title details all customisable.

LICENSING INFORMATION

By using the software product (InControl Sync) contained the final package, you agree to the terms and conditions of this license agreement. Permission is given to the licensee (you) of this product to use the development version of this software under any programming language on one computer at a time, and to make one backup copy. Similarly, if the InControl Sync software is purchased, permission is given to the licensee to use the software on one computer at a time. You may utilize this product for use in your distributed applications. You may distribute and sell any product, which results from using this product in your applications, except a product of similar nature.

This product is sold 'as is', without warranty, implied or expressed. While every effort is made to insure that this product and its documentation are free of defects, Fairport Technologies International shall not be held responsible for any loss of profit or any other commercial damage, including, but not limited to special, incidental, consequential or other damages occasioned by the use of this product.

Fairport Technologies International reserves the right to modify or remove any function, procedure or property, that is not documented in the InControl Sync Developer’s Guide, in future releases of the InControl Sync software. This includes modifying the number and/or type of parameters passed to un-documented functions or procedures.

Fairport Technologies International is not responsible for, nor can we provide technical support for, your use of any un-documented InControl Sync function, procedure or property. You assume full responsibility for supporting your resulting code and component(s) as well as the results of your using any undocumented function, procedure or property.