Bug #16731 | Access violation just to open on a particular database | ||
---|---|---|---|
Submitted: | 23 Jan 2006 16:42 | Modified: | 26 Jan 2006 22:38 |
Reporter: | John Kirkwood | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S3 (Non-critical) |
Version: | 1.1.19 | OS: | Windows (XP SP2 and W2K SP4) |
Assigned to: | CPU Architecture: | Any |
[23 Jan 2006 16:42]
John Kirkwood
[24 Jan 2006 9:40]
Valeriy Kravchuk
Thank you for a problem report. What exact version of MySQL server are you connecting to?
[24 Jan 2006 13:36]
John Kirkwood
Sorry, forgot to mention that. The server v. is v.4.1.15-nt.
[26 Jan 2006 22:38]
Jorge del Conde
I was unable to reproduce this bug connecting to 4.1.15.
[1 Feb 2006 21:43]
Lonnie Best
I have the exact same problem, but I've already posted it here at the bottom (right now): http://bugs.mysql.com/bug.php?id=4329&thanks=3¬ify=7
[2 Feb 2006 14:22]
Berthold Werner
I got the same problem with QB 1.1.19. The error message appears in the third field of the statusline and will be permanently updated. The menues get a darkblue background when moving the mouse over them and cannot be opened. When marking text in the SQLField in gets white letters on white ground. I can do queries on tables and afterwards the updating of the statusline stops and in the second field of the statusline the word "file" appears on darkblue background. When clicking on this field this word and the errormessage disappear. And everything seems to be ok but the menues got still darkblue background, i can open the menues but the disabled option in the menues are not shown. The problem occured some days ago, before this everything was ok. I tried do deinstall and reinstall QB, i tried older versions and deleted the configuration files in applicationdata\mysql but the error persists. I tried connections to MySQL Server versions 5.0.15, 4.1.14 and 4.1.7.
[8 Feb 2006 9:17]
Berthold Werner
I now tried 1.1.20. The error adress changed to 58c7b4. Clicking in the second field of the status line after start removes the error message, menues are now ok.
[15 Feb 2006 7:27]
Berthold Werner
The error disappeard. Perhaps depending on some changes in internet settings(?) Tries the QB to connect to a server at start?