When you move an ADOCE database from the device to an .mdb file on the desktop computer, it has to be converted. Because the H/PC data store is generally less robust than Access, this is a loss-less conversion with the exceptions indicated below. This section describes the conversion process in detail. The converter copies only the tables known to ADOCE.
The following table shows how data types are mapped from ADOCE to an .mdb file.
|
|
|
Sent to desktop computer |
| datetime | Date/Time | sql_timestamp | Yes |
| double | Double | sql_double | Yes |
| integer | LongInt | sql_integer | Yes |
| smallint | Int | sql_smallint | Yes |
| Boolean | YesNo | sql_bit | Yes |
| varbinary | Binary | sql_varbinary | Yes, including length |
| long varbinary | OLEObject | sql_longvarbinary | Yes |
| varchar | Text | sql_varchar | Yes, including length |
| text | Memo | sql_longvarchar | Yes |
Table Conversion
Tables are not converted or copied to the desktop computer if any of the following are true:
No table name conversion is required because the desktop length (64) is larger than the device length (31).
Field Conversion
Field names map one-to-one because the length support on .mdb files and H/PCs are both 64 characters.
Index Conversion
All indexes on the device are created on the desktop computer. If the index on the H/PC has a name beginning with the text “PrimaryKey,” then the index is created as a Unique index. The only other attribute that is used is Ascending or Descending.
Conversion Options
Windows CE filters may have user options. The following table shows the option that is provided for converting .mdb data.
Option |
Default |
Comment |
| Overwrite existing tables | True | If False, then the tables are renamed. By default they are replaced. |
Error Handling
Log entries are written to a file named Ce2db.txt in a process similar to the process for transferring from a desktop computer to a device .