Bug 57207 - VIEWING: data cannot be retrieved with FileMaker ODBC driver 12.3.103a
Summary: VIEWING: data cannot be retrieved with FileMaker ODBC driver 12.3.103a
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
3.6.3.1 rc
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-16 20:54 UTC by Melanie Cotton
Modified: 2014-02-26 19:30 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
the error message received (64.56 KB, image/png)
2012-11-16 20:54 UTC, Melanie Cotton
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Melanie Cotton 2012-11-16 20:54:42 UTC
Created attachment 70175 [details]
the error message received

Problem description: 
Cannot connect to FileMaker database with FileMaker 12 and ODBC driver 12 v3. (all previous version works perfectly)

Steps to reproduce:
1. create a Filemaker database
2. create your dsn using FileMaker driver 12.3.103a and pointing to your FileMaker database. 
3. in LibreOffice, create a query that retrieves data in FileMaker database

Current behavior:
error message appear
"The data content could not be loaded. The execution of the query doesn't return a valid result set."

Expected behavior:
data retrieved

Platform (if different from the browser): 
windows server 2008 for server and windows 7 as the client
              
Browser: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20100101 Firefox/15.0.1
Comment 1 Thomas Hackert 2013-07-05 15:57:18 UTC
Hello Melanie, *,
thank you for reporting this bug :)

But I have some question:
1. What is this FileMaker stuff?
2. Is ODBC in the last available version for Win installed?
3. Is your FileMaker DB installed on the server or the client?
4. Did you test this bug with a newer version of LO than 3.6.3.1 rc? Would you be so kind to test it?

I have neither Win nor FileMaker here, so I cannot be of any further help, sorry ... :( But maybe this bug is fixed in the meanwhile, than see my comment as a reminder ... ;)
Sorry for the inconvenience
Thomas.
Comment 2 QA Administrators 2014-02-02 02:06:23 UTC
Dear Bug Submitter,

Please read the entire message before proceeding.

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
Comment 3 QA Administrators 2014-02-26 19:30:54 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