> I want to move the database to Dialect 3 but I can't figure out the
> source of this error.
> Can anyone suggest a solution?

There are some strange aspects about converting to dialect 3.

- there are possible keyword conflicts that can cause difficulties.

- numeric/decimal fields greater than 9 digits remain as doubles
(whereas the equivalent fields created directly in a d3 database
would be created as int64).

- and other things I cant remember right now.


My recommendation is to try and rebuild the database as dialect 3
rather than converting it. This means you get to detect any
specific problems that may exist, plus it means that your database
will be more consistent.

I have an alternative backup utility (DBak) available at:
http://www.telesiscomputing.com.au/dbk.htm

this may help, as it rebuilds the database via a script extracted
from the source database (and provides an option to change the
dialect for the destination database).


--
Geoff Worboys
Telesis Computing