On 5/30/2011 12:39 PM, heineferreira wrote:

> Hi
>
> The most common way to do database development with Access is via dao or ado. ADO is usually recommended for client/server development but you can use DAO although it is a bit slower. If you want to use bound forms and reports then you should use either of these 2 libraries.
> The easiest way to program Firebird via Access is via odbc linked tables and you can use either of these 2 libraries. Do you know if it's possible to use the MGA with ADO or DAO? Both of these libraries are heavily dependant on locking. I think I can bypass the

There are two models for controlling concurrent access to a database by
multiple user; locking and versioning (also called MGA). The concurrency
control model is implemented entirely within the database engine and is
independent of the data access layer so ADO and DAO are not dependent on
locking.

> locking in a read only environment with passthru queries and by adding a "no lock" into the select statement. I don't know what to do with insert, update and delete statements however. Do you know of a way to achieve this?

You do not have a choice as to whether you use MGA or not. It is built
into the FB engine and is always in operation. You do not have to do
anything with your SQL statements except omit all references to locks.
The only thing you must do is normal transaction management remembering
that FB requires that a transaction be active to read data.

> I know there are commercial ado providers out there but that requires purchasing a licence for every user and I don't even know if they support that functionality. I remember vaguely that Firebird 1.0 had a gds.dll library but I don't know if that's still used.

The Firebird client library has been renamed from GDS32.DLL to
FBCLIENT.DLL. The ODBC driver provides an ODBC interface to FBCLIENT.DLL.

Bill