Summary: | Attempting to write to an ODBC-connected Access 2010 database accdb throws an error and fails | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Alex Thurgood <iplaw67> |
Component: | Base | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED INSUFFICIENTDATA | ||
Severity: | normal | CC: | xiscofauli |
Priority: | medium | ||
Version: | 5.4.1.2 release | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Windows (All) | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 113372 |
Description
Alex Thurgood
2017-10-20 14:58:05 UTC
Hi Alex, Do you reproduce it in previous versions of LibreOffice? @Xisco : people have previously reported functioning systems with 32bit installations of LibreOffice with the 32bit ODBC connectors on Win7/Win8 and Win10, but I haven't (and won't) be testing such setups. I can't say whether this is because it is all 64bit specific, or if something has changed in the way our code accesses the ODBC driver. I can still reproduce this with LO 6011 Is this not the same as *yours* bug 43187? (In reply to Timur from comment #5) > Is this not the same as *yours* bug 43187? No, bug 43187 is about ADO driver usage, not ODBC. (In reply to Alex Thurgood from comment #6) > (In reply to Timur from comment #5) > > Is this not the same as *yours* bug 43187? > > No, bug 43187 is about ADO driver usage, not ODBC. Having said that, I have no way of telling whether the ODBC driver and the ADO driver call the same code path in the underlying LO code, so who knows... The only way to really find out would be to use a debug enabled version and trace the calls...as I'm not putting a debug build on my Win production machine, I guess we will never find out. Hi Alex, Do you still reproduce this issue in master ? Hi Xisco, I can no longer test, I don't have the required set up any more. |