Bug #67408 Excel 2010 crashes with MS Query and filter
Submitted: 29 Oct 2012 11:44 Modified: 30 May 2013 6:57
Reporter: Mike McCormick Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S2 (Serious)
Version:5.2.2 OS:Windows (Windows 7)
Assigned to: Bogdan Degtyariov CPU Architecture:Any
Tags: Excel, filter, MS Query

[29 Oct 2012 11:44] Mike McCormick
Description:
When we connect to a database using the ODBC connector in Excel 2010 the query works fine. But if you try and select a filter in the Query wizard, MS Query crashes straight away.

We have this issue at a client site and also at our office.

How to repeat:
Connect to database from MS Excel using Data, From Other Data Sources, Microsoft Query.

Select your MySQL ODBC datasource.

Select some data, some columns from one or more tables.

Select a column and try to filter (e.g. tableID > 0).

This will crash.
[30 Oct 2012 8:18] Bogdan Degtyariov
I could not repeat the problem using the provided instructions.
Please check the screenshot below. It shows the result in Excel and the query created in MS Query (I am just checking the connection properties after querying data). As you can see the query has the WHERE clause and no crash happened.

Maybe it occurs on a specific column or data set. Can you please send the CREATE TABLE statement for your table along with the sample data?
[30 Oct 2012 8:19] Bogdan Degtyariov
Screenshot showing data sheet and query in Excel

Attachment: excel_query_result.png (image/png, text), 78.13 KiB.

[30 Oct 2012 9:15] Mike McCormick
Filter Data Screen from Query Wizard

Attachment: FilterDataScreen.png (image/png, text), 33.53 KiB.

[30 Oct 2012 9:18] Mike McCormick
Hi,

I understand you can edit the SQL to get filtering to work but this occurs in the Wizard when you get to the 'Query Wizard - Filter Data' screen. I have attached a screenshot to the submission.

I realise there are a couple of workarounds for this but we have a dozen users who want to have the ease of use of the Wizard to create their own Excel reports.

Many thanks,

Mike.
[1 Nov 2012 11:17] Bogdan Degtyariov
Hi Mike,

Thanks for your reply.
I used the query wizard to filter data (please check the screenshot).
It looks that the crash depends on the data structure.
Does it crash for you even in simplest tables?

For instance:

CREATE TABLE t1 (id int primary key, vc varchar(32));
INSERT INTO t1 (id, vc) VALUES (1, "One"), (2, "Two"), (3, "Three");
[1 Nov 2012 11:18] Bogdan Degtyariov
Query Wizard - Filter Data

Attachment: query_wizard_filter.png (image/png, text), 10.65 KiB.

[1 Nov 2012 20:22] Mike McCormick
Hi,

I created a new database and the new table as you specified.
Then a new ODBC connection.
I still get the error.

I have attached 2 screenshots. One show the crash. The other shows the point at which it occurs. You can select a field to filter and as soon as you try to select a value from the final dropdown it crashes.

I appreciate your help on this.

Many thanks,

Mike.
[1 Nov 2012 20:23] Mike McCormick
Crash

Attachment: MSQueryCrash.jpg (image/jpeg, text), 26.42 KiB.

[1 Nov 2012 20:25] Mike McCormick
Filter screen

Attachment: FilterScreen.jpg (image/jpeg, text), 40.06 KiB.

[2 Nov 2012 10:03] Bogdan Degtyariov
Mike,

I still cannot get it to crash.
Please check the screenshot with open pop-up values for vc column.

What options do you have in the ODBC Data Source for this connection?
You can check this by running the following command:

C:\Program Files (x86)\MySQL\Connector ODBC 5.2\ANSI>myodbc-installer.exe -s -l -c2 -n "test52a"

The output should be looking as follows (please remember to manually remove or asterisk the uid and pwd just as I did):

Name:                test52a
Driver:              C:\Program Files (x86)\MySQL\Connector ODBC 5.2\ANSI\myodbc5a.dll
Server:              localhost
Uid:                 *********
Pwd:                 *********
Database:            test
Port:                3306
Options:
[2 Nov 2012 10:03] Bogdan Degtyariov
Query Wizard - Filter Data pop-up values

Attachment: query_wizard_filter_dropdown.png (image/png, text), 7.03 KiB.

[5 Nov 2012 13:21] Mike McCormick
Hi Bogdan,

I don't know if this helps but the exe file is not in 'ANSI' but 'unicode' and the dll I have associated with the ODBC driver is MYODBC5W.DLL. Port, serverm etc. all look fine.

Many thanks,

Mike
[15 Nov 2012 11:28] Bogdan Degtyariov
Mike,

The situation is not quite clear for me so, can you please send me the output from myodbc-installer as asked in my message from 2 Nov?
[16 Dec 2012 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[30 May 2013 6:57] Bogdan Degtyariov
I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.
[13 May 2016 19:09] Jerry Travis
How to create MySQL Bug# 67408

Attachment: $MySQL_Bug# 67408.doc (application/msword, text), 137.50 KiB.

[13 May 2016 19:10] Jerry Travis
I'm having the same issue as originally described in this ticket. Client is MS Windows 7 and Office 2010. Database is MySQL Server version 5.6.19-67. Though commonly thought to be an Excel problem, the trouble is in Microsoft Query itself. If you start it standalone from C:\Program Files (x86)\Microsoft Office\Office14\MSQRY32.EXE and create a query using the Query Wizard, then set a filter in the (Query Wizard - Filter Data) popup using the List of Values pulldown on the far right, Microsoft Query will immediately terminate with the Error, "Microsoft Query as stopped working". A detailed procedure on how to create the error, along with screen shots, is in the attached file. Below is the application error from the Event Viewer.
[13 May 2016 19:12] Jerry Travis
Log Name:      Application
Source:        Application Error
Date:          5/13/2016 11:48:11 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ZAS-W7STNVM090.Zenith-American.Local
Description:
Faulting application name: MSQRY32.EXE, version: 14.0.7010.1000, time stamp: 0x511cfec4
Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace5b9
Exception code: 0xc0000417
Fault offset: 0x000320f0
Faulting process id: 0x1994
Faulting application start time: 0x01d1ad47f0e58c2b
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\MSQRY32.EXE
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
Report Id: 3d91a0eb-193b-11e6-871c-eeabcdfda3c2
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-05-13T18:48:11.000000000Z" />
    <EventRecordID>170574</EventRecordID>
    <Channel>Application</Channel>
    <Computer>ZAS-W7STNVM090.Zenith-American.Local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>MSQRY32.EXE</Data>
    <Data>14.0.7010.1000</Data>
    <Data>511cfec4</Data>
    <Data>MSVCR90.dll</Data>
    <Data>9.0.30729.6161</Data>
    <Data>4dace5b9</Data>
    <Data>c0000417</Data>
    <Data>000320f0</Data>
    <Data>1994</Data>
    <Data>01d1ad47f0e58c2b</Data>
    <Data>C:\Program Files (x86)\Microsoft Office\Office14\MSQRY32.EXE</Data>
    <Data>C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll</Data>
    <Data>3d91a0eb-193b-11e6-871c-eeabcdfda3c2</Data>
  </EventData>
</Event>