Article ID: 196034 - Last Review: March 14, 2005 - Revision: 2.3 HOWTO: Use ADOFILTR.DLL to Transfer Database TablesThis article was previously published under Q196034 On This PageSUMMARY
This article demonstrates how to use the ADOCE API (the ADOFILTR.DLL
exports) in Visual Basic to programmatically import and export data tables
between the desktop and a remote device.
MORE INFORMATION
ADOFILTR.DLL, Pocket Access file converter and synchronizer, is a part of
the ActiveX Data Objects 2.0 SDK for Windows CE (ADOCE 2.0). It allows
programmatic transfer of database tables between the host desktop computer
and the remote device. It runs on the desktop computer, not the remote
device. The desktop initiates and controls the transfer process. For
additional information on ADOCE 2.0, please see the following article in
the Microsoft Knowledge Base:
238947
(http://support.microsoft.com/kb/238947/EN-US/
)
FILE: Msadoce2.exe Installs ADO for Windows CE SDK
The sample code provided below transfers a table in the Biblio.mdb sample
database between the desktop and the remote device. Before trying this
sample, you need to make sure that ADOCE 2.0 is already installed on the
remote device.
Modify Biblio.MDBReferential integrity rules may interfere with table import. Therefore, the Biblio database must be modified to have a table without relationships. You can use the Visual Data Manager add-in in Visual Basic to modify Biblio.MDB and create a new table.
Create the Project to Import and Export Tables
-2147024894 The remote device may not be connected properly, or ADOCE
1.0 was not installed or registered correctly on the
remote device. To install ADOCE 1.0 on the remote device,
you need to click on Start, Programs, Microsoft ADOCE 1.0
and then Install ADOCE on HPC while the device is
connected to the desktop machine and communication is OK.
-2146824447 The destination table may already exist on the desktop and
Overwrite was set to False, or Overwrite was set to True
but the table is not allowed to be overwritten. A log file
may also display.
-2147217865 This error may occur if an attempt is made to import a
table does not exist from the remote device.
NOTE: The values above are the result of subtracting the vbObjectError constant from the raw error value. REFERENCES
Microsoft Windows CE ActiveX Data Objects SDK 2.0 Help
APPLIES TO
| Article Translations
|

Back to the top
