| Summary: | Failed to insert record by ODBC Access2Base | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Diego Ariel <d.a.capeletti> |
| Component: | BASIC | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEEDINFO --- | QA Contact: | |
| Severity: | major | ||
| Priority: | medium | CC: | iplaw67, serval2412 |
| Version: | 4.2.1.1 release | ||
| Hardware: | All | ||
| OS: | Windows (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | Code, database and application. | ||
|
Description
Diego Ariel
2014-04-03 15:33:22 UTC
Created attachment 96860 [details]
Code, database and application.
I use Windows XP with Libreoffice 4.2.1.1 I'm migrating a front end from Ms Access based Libreoffice. The database is Ms accces (. Accdb). I use ODBC to communicate with the front end database. The driver is Ms database engine. When I run the procedure that contains the code access2base no error message, but the data is inserted. Using another method that does the same but with the LibreOffice API, the process is carried out correctly. I think it is an unfair warning Access2Base. Steps to reproduce the problem are: 1- Create an ODBC connection pointing to the database. 2- Copy the code to a front end file that uses the odbc connection. 3- Run the procedure to see the unfair warning. This warning does not appear when you run the procedure that makes use of the API libreoffice. El mismo procedimiento utilizado por Acces2Base, el error que aparece cuando se utiliza ODBC con MS Access, no aparece en HSQLDB. The same procedure used by Acces2Base, the error that appears when using ODBC with MS Access, does not appear in HSQLDB. *** Bug 77017 has been marked as a duplicate of this bug. *** Access2Base has been updated in these last months, see http://cgit.freedesktop.org/libreoffice/core/log/?qt=grep&q=access2base Do you reproduce the problem with last stable LO version, 4.3.5? Adding self to CC if not already on |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.