A perfectly working BASIC macro, that uses Access2Base Tools Library, has stopped working when the table used to get a recordset (single record or whole table for cloning) has boolean fields.
"Select" instruction works fine, but when you try to use the recordset boolean field or try to clone the recordset, Access2Base throws an exception and the macro now is no more working
Steps to Reproduce:
1. Open the attached example database
2. Run the macro "BugBooleanFieldsOne" to reproduce recordset read value bug
3. Run the macro "BugBooleanFieldsTwo" to reproduce recordset clone bug
AccessToBase throw an exception
No errors, field boolean value correctly read and cloned recordset created
User Profile Reset: No
No other info
Created attachment 165965 [details]
Database with macro to test bug
This database works with LO 6.4.6.x and all previous version using Firebird embedded databse
Jean-Pierre: thought you might be interested in this one since it concerns Access2Base.
I confirm the incorrect behaviour in LO 7.0.1, and also the correct behaviour in previous releases, incl. 126.96.36.199.
A similar issue has been documented in tdf#136063.
The symptoms are different from the current issue, but their root causes are identical.
The real issue has been documented in tdf#136143. A correction has been implemented in master (LO 7.1) and in 7.0.
The latter will be available in LO 7.0.2.
I tested the here described issue under a recent build of 7.1 and can confirm that the behaviour is now correct. I could however not run it on a build of 7.0.2.
Thanks for having reported this regression.
*** This bug has been marked as a duplicate of bug 136143 ***