![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM ODBC Driver » View Thread |
Messages 1 to 2 of 2 total |
![]() |
Wed, Mar 17 2021 10:00 AM | Permanent Link |
Darren | 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 |
Wed, Aug 4 2021 6:49 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | 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 |
This web page was last updated on Monday, July 15, 2024 at 07:03 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |