I just started trying FireDAC with the DBISAM odbc driver (4.49 b4) and am having issues with 64 bit compiles, but not 32 bit.

Scenarios:
1. Table1 has primary index that is compound and includes a timestamp field.
Both a FDQuery and FDTable get A/V when opening table.

2. Table1 has primary index that is not compound and only includes a timestamp field.
Both FDQuery and FDTable open fine.

3. Table1 has a non primary index that contains a timestamp field.
FDQuery opens fine, FDTable gets A/V.

The access violations:

Primary Key: (FireDac.phys)
       oPKFieldsView := oConnMeta.GetTablePrimaryKeyFields(GetCatalogName,
         GetSchemaName, sTabName, '');

Secondary Key: (FireDAC.comp.client)
       oVInds := oConnMeta.GetTableIndexes(CatalogName, SchemaName, TableName, '');


I tried this in Berlin and Sydney getting an A/V in each.

Any ideas? Am I doing something wrong with regards to building in 64 bit?

Thanks

Housekeeping: this was resolved per this incident report:

https://www.elevatesoft.com/incident?action=viewaddr&category=dbisam&release=4.49&incident=4827

Tim Young
Elevate Software
www.elevatesoft.com