Hi
I use WIN1250 charset.
If the database charset is specified in ODBC connection parameter, shouldn't be any problems.

SQLSTRINGCONNECT([PROVIDER=MSDASQL;DRIVER=Firebird/InterBase(r) driver;
DBNAME={server}:{database_full_path};UID={user};PWD={password};CHARSET=WIN1250])

The 1.5 version is based on C++ port. As enhancements (only few, but there are more): improved speed (40-60%), database aliases, folder restrictions if needed, custom named constraints for previously auto-generated, generic triggers for all operations are possible, CASE, COALESCE, NULLIF in SQL and PL/SQL, SQL99 savepoins (nested transactions), explicit locking if needed, group by UDF, runtime exceptions messaging.

Have fun - the need for ; at the end of command in PL will bite you :-)


>Thanks once more.
>And last questions - what collation/char set you use. Did you have a problem with using extended ASCII characters while inserts and updates ?
>
>I created Firebird database made connection to it and create table from within VFP without problem but when I tried to do insert - ODBC shows error indicating that it has problem with translating chars. To be honest I did not spend to much time to solve the problem, maybe I just missed something obvoius. I use 1.03 version maybe I should try 1.5 - what are main new fetures of 1.5 version?
>
>
>
>>We switched to 1.5 when was Release Candidate 5.
>>For the project I'm working on now, I use version 1.5, because of new features. This month I think that will be the final release.
>>
>>One thing, don't use .GDB extension for databases. For some reasons, .GDB extension is included in System Restore stuff. All database operations will be slowed down (connections, updates). I'm sure that this has nothing to do with the fact that is the default extension for Interbase databases and Interbase is broadly used :-)
>>
>>
>>>Great thanks !
>>>
>>>What version you use - 1.0 or 1.5 ?
>>>
>>>
>>>>
>>>>1. We use the IBPhoenix open source ODBC driver , www.ibphoenix.com. No problems so far.
>>>>The connection string is:
>>>>lnFBSqlConnH = SQLSTRINGCONNECT([PROVIDER=MSDASQL;DRIVER=Firebird/InterBase(r) driver;DBNAME={server}:{database_full_path};UID={user};PWD={password}])
>>>>for versions 1.0 and 1.5
>>>>
>>>>or
>>>>
>>>>lnFBSqlConnH = SQLSTRINGCONNECT([PROVIDER=MSDASQL;DRIVER=Firebird/InterBase(r) driver;DBNAME={server}:{database_alias};UID={user};PWD={password}])
>>>>only for 1.5.
>>>>
>>>>2. (DATE - as in VFP, TIME - no equivalent, TIMESTAMP = fox DATETIME. No, it doesn't allow empty dates, but allow null in columns.
>>>>
>>>>I recommend you IBExpert, the free personal edition, for a start. It is a nice tool.