Bug #22730 MySql Query Browser: Access Violation at address 005CA7B0

• Submitted: 27 Sep 2006 8:58
• Modified: 4 Oct 2006 7:38
• Reporter: Hou Lei
• Status: Duplicate
• Category: MySQL Query Browser
• Severity: S3 (Non-critical)
• Version: 1.2.3
• OS: Windows (Windows Server 2003)
• CPU Architecture: Any

[27 Sep 2006 8:58] Hou Lei

Description:
I have downloaded and installed the latest version of the following:

MySQL Server 5.0.24 Community Version
MySQL GUI Tools Bundle for 5.0 which includes:
- MySQL Administrator 1.2.3rc
- MySQL Query Browser 1.2

Upon startup of the Query Browser, the following error message appears at the status bar at the bottom of the screen:

Access Violation at address 005CA7B0 in module "MySQLQueryBrowser.exe" Read of address 00000000.

At this stage, I am able to view the Schema and it's tables and views on the right hand panel.  However, I am not able to use the tool bar at the top of the screen, ie. "File, Edit, etc"

If, however, at this point, if I run and execute a query, it shows the results/rows as normal, and then the tool bar at the top becomes useable again.

Although the programme seems to be working at the point, the error message remains on the status bar at the bottom of the screen.

The tried connecting to different default schemas upon startup and the error message is still displayed.

How to repeat:
Run MySQL Query Browser and the error message will appear at the status bar at the bottom of the screen.  

Suggested fix:
I have read about this problem in your forum and tried the suggested solution:

http://forums.mysql.com/read.php?108,7923,59159#msg-59159

However, my MySQL Administrator does not seem to save any changes I make, even though I clicked on the "Apply Changes" button.

Please suggest what I could do.  Many thanks.

[4 Oct 2006 7:38] Sveta Smirnova

Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicates bug #21001