Hi Simona,
> we have 64-bit systems
32-bit TestComplete runs perfectly fine on 64-bit systems. So I would not consider the necessity to use 32-bit TestComplete as a showstopper.
> TestComplete is opened with x86 version
x86 means 32-bit version.
> Is not existing a way to interact within a database using the 64-bit Test Complete?
General architecture is like this:
-- TestComplete talks to ADO layer (you may use either pure ADO objects or ADODB wrapper provided by TestComplete as is done in your code sample). It is required for TestComplete and ADO to have same bitness (actually, as ADO is provided by the OS, it guarantees that both 32-bit and 64-bit ADO objects are installed);
-- ADO uses provided connection string and talks either to corresponding data provider or to ODBC. ADO data provider is a component that might be either installed by the system (like SQL Server data provider) or by the end-user (for specific data sources, like SQLLite in your case). It is required for data provider to be of the same bitness as ADO (and TestComplete) because ADO can communicate with data providers/ODBC drivers of the bitness that matches bitness of ADO layer;
-- Data provider or ODBC driver talks to data source and provides or manipulates with data source data. Usually, data providers of some bitness can communicate with data sources of different bitness.
Considering the above, you must look for either ADO data provider or ODBC driver that:
a) Provides you with required functionality; and
b) Has bitness that is convenient for you.
If data provider or ODBC driver exists only of certain bitness then you have no other way but use TestComplete of the bitness that matches the bitness of data provider/ODBC driver.
