Description: In old 6.1.2 i made some large mail merge documents based on foxpro databases imported in odb via ODBC driver. It was working almost fine ... I updated yesterday to 6.1.4.2 ... Writer mail merge return empty fields, Base show empty tables ... something is wrong with odbc. Steps to Reproduce: 1.create a db table with name c(20), surname c(20), append ("Popescu","Vasile"),("Ionescu","Ion") 2.create odb baze , connect by odbc, microsoft visual foxpro driver, show folder, register the database name g 3.create .ott document, open database, drag field <nume>, filed <prenume> 4.try print say yes to mail merge Actual Results: no fields values in print Expected Results: to be values ... Reproducible: Always User Profile Reset: No Additional Info: As a suggestion ... Mail merge should ask and print fields values also at print preview ! In prev version, at print preview it's printing field names ... :(
I suspect that this is a duplicate of 120695 - it seems that ODBC in general is no longer able to retrieve data.
(In reply to Alex Thurgood from comment #1) > I suspect that this is a duplicate of 120695 - it seems that ODBC in general > is no longer able to retrieve data. May I correct you? ODBC _is_ able to retrieve data (ODBC client gets data correctly). LO isn't able to retrieve data from ODBC data source.
(In reply to verlata from comment #2) > May I correct you? ODBC _is_ able to retrieve data (ODBC client gets data > correctly). LO isn't able to retrieve data from ODBC data source. Yes, I should have been more precise - the ODBC bridge via LO is no longer able to retrieve and display data.
Hmm, so testing on Version: 6.1.4.2 Build ID: 9d0f32d1f0b509096fd65e0d4bec26ddd1938fd3 CPU threads: 8; OS: Mac OS X 10.14.2; UI render: default; Locale: fr-FR (fr_FR.UTF-8); Calc: group threaded connecting to mysql via ODBC works for me, I can retrieve and edit data, so is this report perhaps specific to either the Foxpro ODBC driver, or Windows OS ? @Dandy66 : in the sample table construction, you don't appear to have a primary key index - it is my understanding that this is required in order for LO to load and index the dataset and use a row cursor to navigate through the result set.
Dear Dandy66, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/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 MassPing-NeedInfo-Ping
Dear Dandy66, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp