Please note: this article is still under construction, and more information will be added shortly.
The HanDBase Conduit leaves messages in the HotSync log (for Palm OS devices)
or the HanDBase ActiveSync log (for Pocket PC devices and Windows-based
SmartPhone devices) in response to certain events. The following list defines
the meaning of the different messages. Note that in the messages below, a
will have the name of the HanDBase database in question.
HanDBase version 3.0 or greater must be installed on your handheld
device | This can occur if you HanDBase 3 is not in device memory on the
Palm OS device (if you chose to install HanDBase 3 to a memory card on a Palm OS
device instead of installing the program to device memory, or if you deleted the
HanDBase 3 program from the handheld). |
No installed HanDBase license keys that are valid and required for
this product to run. | This can occur if you run the install program
for the HanDBase Conduit, HanDBase Plus, HanDBase Professional or HanDBase
Enterprise while you are logged in to Windows with one user account (such as the
Windows admin account), and then log in to Windows as a different user in order
to perform the synchronization with the handheld. You need to run the install
program while you are logged in to Windows as the Windows user that will be
using the software. |
SyncExchange failed to execute properly on this
database | There is no specific known cause for this, and it is
recommended that you contact technical support at support@ddhsoftware.com for
assistance. |
The desktop database '' has been replaced with the
corresponding handheld database, since 'handheld overwrites desktop' is set for
this database | This means that you added the database to
Sync
Exchange, used the Sync Options button, and specified the option 'handheld
overwrites desktop'. This means that the handheld copy of the HanDBase database
will completely overwrite the desktop copy during the synchronization (as
opposed to merging the changes in both directions between the handheld and
desktop copy) |
The handheld database '' has been replaced with the
corresponding desktop database, since 'desktop overwrites handheld' is set for
this database | This means that you added the database to
Sync
Exchange, used the Sync Options button, and specified the option 'desktop
overwrites handheld'. This means that the desktop copy of the HanDBase database
will completely overwrite the handheld copy during the synchronization (as
opposed to merging the changes in both directions between the handheld and
desktop copy) |
The handheld database '' was not updated since the
'one way sync: handheld to desktop' option is set for this
database | This means that you added the database to
Sync
Exchange, used the Sync Options button, and selected the option the option
'one way sync: handheld to desktop'. This means that the changes to the records
in the database that are made on the handheld will update the corresponding
desktop copy of the database, but any changes that are made to that database on
the desktop will not be updated to the handheld copy. This is different than
the option 'handheld overwrites desktop' because with 'one way sync: handheld to
desktop' the actual database file on the desktop does not get overwritten. |
The desktop database '' was not updated since the
'one way sync: desktop to handheld' option is set for this
database | This means that you added the database to
Sync
Exchange, used the Sync Options button, and selected the option the option
'one way sync: desktop to handheld'. This means that the changes to the records
in the database that are made on the desktop will update the corresponding
handheld copy of the database, but any changes that are made to that database on
the handheld will not be updated to the desktop copy. This is different than the
option 'desktop overwrites handheld' because with 'one way sync: desktop to
handheld' the actual database file on the handheld does not get
overwritten. |
The handheld database '' has been replaced with the
corresponding desktop database, since the structure of the database has
changed | |
The desktop database '' has been replaced with the
corresponding handheld database, since the structure of the database has
changed | |
'Backup on hotsync' unset for both the desktop and handheld
database. Database '' not being synchronized | This
refers to one of the options in the General properties in the database
properties of a HanDBase database. On a Palm OS device, the General properties
include the option "sync/backup database". If the checkmark is removed from
that option, then changes that are made in this database will not synchronized
between the handheld and desktop, and you will see a notification in the sync
log as a reminder. |
HanDBase warning: database '' is being processed by a
Sync Exchange entry. Default Palm conduit setting may be ignored | This
literally means that the database has been added to Sync
Exchange. You will receive this message for any database that has been added to
Sync Exchange every time you synchronize with the HanDBase Conduit. |
ODBC Table Schema does not match HanDBase schema - column name
mismatch | See the article http://www.ddhsoftware.com/knowledgebase.html?UID=202505080354583.145.116.193&read=280 for details. |
ODBC Table Schema does not match HanDBase schema - column type mismatch | See the article http://www.ddhsoftware.com/knowledgebase.html?UID=202505080354583.145.116.193&read=280 for details. |
| Microsoft Access 'autonumber' fields cannot be synchronized. Remove these columns from the column list. | See the article http://www.ddhsoftware.com/knowledgebase.html?UID=202505080354583.145.116.193&read=233 for details. |
If you have set up a database to synchronize with an external data source, like
MS Access, through Sync Exhange, you may encounter the following messages in the
sync log. These messages are generated by the external data source, and
reported in the sync log. For example, if you have set up a HanDBase database
in Sync Exchange to sync with an Access table, but Microsoft Access rejects the
creation of a new record for some reason, Access could generate an error, report
the error to the HanDBase Conduit, and then the HanDBase Conduit would report
the error from Access in the sync log. These are some of the known errors
created by MS Access or other data sources, with their possible meanings.
The changes you requested to the table were not successful because they
would create duplicate values in the index, primary key, or relationship. Change
the data in the field or fields that contain duplicate data, remove the index,
or redefine the index to permit duplicate entries and try
again. | The particular Access table (that you specified for that HanDBase
database to synchronize with via Sync
Exchange) is set up with an index or primary key, meaning that there is a
particular field in that Acccess table that is set up in a way that no two
records in the table can have the same value. If you create a new record in
the HanDBase database that would create two records with the same value for that
field, then Microsoft Access will reject the record with the duplicate
value.
For further information on this, see "A synchronization between a
HanDBase database and an Access table results in a complete set of duplicate
records in either the HanDBase database or the Access table, or both." at http://www.ddhsoftware.com/knowledgebase.html?UID=202505080354583.145.116.193&read=281 |
Too few parameters. Expected 2. | There are two
possibilities.
If you specify a query in Access, instead of a table, you
will receive a message like this. Sync Exchange does not support synchronization
to queries. Sync Exchange specifically works with Access tables, not
queries.
Check to see if any of the fields in the Access table has a question mark,a
pound sign (#), exclamation point (!) and some other non-alphanumeric characters
have special meaning in Access or any other special characters in the field
names. If so, remove the question marks or other special characters from the
field names, and the error should go away.
The Access driver (the software interface to Access from third party
applications, like HanDBase) can misinterpret field names that have a question
mark, thinking the question mark is an indication of a parameter that will be
given to Access, such as when you run a query. If you use those kinds of
characters in field names or table names, Access may have a problem performing
some actions, depending on the action. |
|
