Download it now!
Bug 77012 - Failed to insert record by ODBC Access2Base
Summary: Failed to insert record by ODBC Access2Base
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
4.2.1.1 release
Hardware: All Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 77017 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-04-03 15:33 UTC by Diego Ariel
Modified: 2015-09-04 03:01 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Code, database and application. (19.12 KB, application/gzip)
2014-04-03 17:26 UTC, Diego Ariel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Diego Ariel 2014-04-03 15:33:22 UTC

    
Comment 1 Diego Ariel 2014-04-03 17:26:14 UTC
Created attachment 96860 [details]
Code, database and application.
Comment 2 Diego Ariel 2014-04-03 17:34:32 UTC
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.
Comment 3 Diego Ariel 2014-04-04 11:42:14 UTC
El mismo procedimiento utilizado por Acces2Base, el error que aparece cuando se utiliza ODBC con MS Access, no aparece en HSQLDB.
Comment 4 Diego Ariel 2014-04-04 11:42:40 UTC
The same procedure used by Acces2Base, the error that appears when using ODBC with MS Access, does not appear in HSQLDB.
Comment 5 sophie 2014-04-15 13:49:09 UTC
*** Bug 77017 has been marked as a duplicate of this bug. ***
Comment 6 Julien Nabet 2014-12-30 09:45:54 UTC
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?
Comment 7 Alex Thurgood 2015-01-03 17:39:20 UTC
Adding self to CC if not already on
Comment 8 QA Administrators 2015-07-18 17:35:47 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team

This NEEDINFO message was generated on: 2015-07-18
Comment 9 QA Administrators 2015-09-04 03:01:08 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO
Message generated on: 2015-09-03