>>> OK, Action was a bad choice of field name, but this was not ourselves
>>> but
>>> the company that
>>> provides this software, iSoft.
>>> Is the only option then to change the database to dialect 3?
>>> Is that possible?
>>
>>Yes, you can do that -
>>
>>One is to create a backup and restore it under dialect 3, this is a
>>completely new database, dialect 3 wise.
>
> No can do. Only gfix can change that bit of the header; but doing that
> will make it so that the database header has wrong information about the
> data that is stored in the database. Changing the dialect bit does NOT
> upgrade the data.
>

Woops, my bad, I just checked and it isn't possible! Sorry Bart.

>>The other is to adjust it's settings to be dialect 3 "from now on", DBW
>>allows
>>you to do that if you select "Database Properties" from the Enterprise
>>Manager.
>
> That will break the existing dialect 1 data. Also, if they are using
> proprietary software, the client will be connecting with dialect 1.

As Thomas said so.

> I think they should get iSoft to fix it. Upping the dialect on an
> existing database is not a trivial thing to do.

With regards,

Martijn Tonies
Upscene Productions
http://www.upscene.com

Download Database Workbench for Oracle, MS SQL Server, Sybase SQL
Anywhere, MySQL, InterBase, NexusDB and Firebird!