| Question 1 | I get the message: The requested feature [idbschemarowset::getschema] is available in the commercial version of IBProvider [www.ibprovider.com] only |
| Question 2 | I get the message while connecting to the Interbase database: Free IBProvider can't work with Database Server (1) Version (2). Original Server ID=(3). Support of this RDBMS is available in the commercial version of IBProvider [www.ibprovider.com] only. |
| Question 3 | Does IBProvider provide access Firebird Delphi and Interbase Delphi? |
| Question 4 | When I do a simple SQL SELECT, I get an error saying "Automatic transaction is disabled". Do you have any ideas? |
| Question 5 | Is it possible to combine "auto_commit" with manual transaction handling? |
| Question 6 | How to set such specific for IB/FB properties of transaction as for example "wait" and "no wait"? |
| Question 7 | Why doesn't connection pool work? |
| Question 8 | What are the required initialization parameters for using IBProvider as linked SQL server? |
| Question 9 | What's the difference between Free and commercial versions? |
| Question 10 | Why do opening rowsets have the attribute read-only? |
| Question 11 | While using IBProvider v2 in ADOExpress the server cursor doesn't work. It works in the first version. |
| Question 12 | Why my active connections are still alive? There were no such occurrences before. |
| Question 13 | Does IBProvider can work with Microsoft Visual Studio .Net? |
| Question 14 | Can I use named parameters in ADO.Net? |
|
Question 1: |
I get the message: The requested feature [idbschemarowset::getschema] is available in the commercial version of IBProvider [www.ibprovider.com] only |
|
IBProvider Free Edition has functional restrictions: metadata schemas and Interbase DBMS greater than 6 version are not supported. To avoid such messages please use IBProvider Professional Edition .
|
|
Question 2: |
I get the message while connecting to the Interbase database: Free IBProvider can't work with Database Server (1) Version (2). Original Server ID=(3). Support of this RDBMS is available in the commercial version of IBProvider [www.ibprovider.com] only. |
|
Only IBProvider Professional Edition provide access to the Interbase database greater than 6 version.
|
|
Question 3: |
Does IBProvider provide access Firebird Delphi and Interbase Delphi? |
|
There are 3 way for access to Interbase and Firebird from Delphi (RAD Studio): - dbGo (ADO Express) components provide access via ADO library.
- Direct access to COM-interfaces of ADO library.
- Direct access to OLE DB-interfaces using 3rd party components (OLE DB Direct/OLE DB Express).
See examples of using Firebird and Interbase from Delphi via ADO + MTS: Firebird Delphi and Interbse Delphi
|
|
Question 4: |
When I do a simple SQL SELECT, I get an error saying "Automatic transaction is disabled". Do you have any ideas? |
|
For work in "auto-commit" mode, you should set "auto_commit = true" in connection string or set "SessionAutoCommit = true" session's property if connection was created already. You may use other mode. See news about it. You may use ADODB.Connection.BeginTrans or start_transaction (for ADO or C++). For more information read examples.
|
|
Question 5: |
Is it possible to combine "auto_commit" with manual transaction handling? |
|
Yes, you can handle transactions manually in "auto_commit" mode. IBProvider begins transactions if only there are no started transaction in current session.
|
|
Question 6: |
How to set such specific for IB/FB properties of transaction as for example "wait" and "no wait"? |
|
This properties can be set only with the starting of transactions through SQL commands (see ADO sample)
For obtaining the more detailed information look in IB/FB documentation syntax of "SET TRANSACTION" command.
|
|
Question 7: |
Why doesn't connection pool work? |
|
The property "...;free_threading=true" is not indicated in the connection string
|
|
Question 8: |
What are the required initialization parameters for using IBProvider as linked SQL server? |
|
They are: "user id=gamer;password=vermut;free_threading=true;truncate_char=false;..."
|
|
Question 9: |
What's the difference between Free and commercial versions? |
|
The differences between version here
|
|
Question 10: |
Why do opening rowsets have the attribute read-only? |
|
Most probably you use Free IBProvider. In this version the columns of the result rowset don't have the attribute permitting writing. The commercial version has this attribute.
|
|
Question 11: |
While using IBProvider v2 in ADOExpress the server cursor doesn't work. It works in the first version. |
|
The problem is in ADOExpress. These components can't work with 8-bytes rows bookmarks used in IBProvider v2. In the first version (also included into the distribution kit of the commercial version) 4-bytes bookmarks, supported by ADOExpress are used. That's why when working with the second version through the ADOExpress you can use only ClientCursor. Also you can use another access VCL-components which have no such restriction, for example, OLEDBDirect.
|
|
Question 12: |
Why my active connections are still alive? There were no such occurrences before. |
|
Most probably "before" is earlier than build no. 969 (2.2 and 1.7.17). From this build the connection pool is enabled by default ("free_threading" property is true). Set "free_threading" to false for disabling connection pool.
|
|
Question 13: |
Does IBProvider can work with Microsoft Visual Studio .Net? |
|
Yes of course. IBProvider is support all Ole Db Interfaces, which required for Visual Studio .Net . Look in the samples.
|
|
Question 14: |
Can I use named parameters in ADO.Net? |
|
IBProvider is support named parameters, but ADO.Net library is support only positional parameters for Ole Db and ODBC data providers. You can use named parameters, but then you adding its into the parameters collection use sequence that definded in the OleDbCommand.CommandText. Set Parameters values can be arbitrarily. For example:
\\define OleDbCommand with two named parameters (:name and :id)
OleDbCommand.CommandText ="update employers set name=:name where id=:id"
\\adding parameters using sequence that definded in OleDbCommand.CommandText
OleDbCommand.Parameters.Add("name",OleDbType.VarChar);
OleDbCommand.Parameters.Add("id",OleDbType.Integer);
\\arbitrarily set parameters data
OleDbCommand.Parameters["id"].Value = NewID;
OleDbCommand.Parameters["name"].Value = "Some name";
|
