Edit select statement in TMyQuery bug

Discussion of open issues, suggestions and bugs regarding MyDAC (Data Access Components for MySQL) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
kaffeburk
Posts: 214
Joined: Mon 29 Jan 2007 08:03

Edit select statement in TMyQuery bug

Post by kaffeburk » Wed 22 Jun 2011 17:33

When i get to "MyQuery Editor.." of a TMYQuery i cant enter the select from my keyboard. If i press the M key i get redirected to the "Macro Tab" if im in stored procedure and hit M I get the same problem.

Same with the other keys that have a corresponding tab. I been having the problem for years, on various computers, but just typed the SQL somewhere else and pasted it in...

It doesn't matter if i have Swedish or English keyboard input.

AndreyZ

Post by AndreyZ » Thu 23 Jun 2011 13:44

Hello,

I cannot reproduce this problem. Please specify the following:
- the exact version of your IDE;
- the exact version of MyDAC. You can learn it from the About sheet of TMyConnection Editor.

kaffeburk
Posts: 214
Joined: Mon 29 Jan 2007 08:03

Post by kaffeburk » Thu 23 Jun 2011 16:31

AndreyZ wrote:Hello,

I cannot reproduce this problem. Please specify the following:
- the exact version of your IDE;
- the exact version of MyDAC. You can learn it from the About sheet of TMyConnection Editor.
Delphi® 2007 for Win32® Version 11.0.2804.9245 (update 3)
Mydac 6.10.3.8

But i had this problem since Delphi 7, and also with earlier versions of Mydac, back to Mydac 4. Also with Vista, xp and windows 7 (32 and 64). With laptops, stationary with 32 and 64 bit Pentium.

Once the "code completion" kicks in, it wont happen. But if im in the SQL tab and press U, G, P, M or T i will move to the corresponding tab.

kaffeburk
Posts: 214
Joined: Mon 29 Jan 2007 08:03

Post by kaffeburk » Thu 23 Jun 2011 18:07

1 more detail: When i open up the "MyQuery Editor", the shortcuts is not underlined, but as soon as i hit any shortcut key they all get underlined and stay that way.

AndreyZ

Post by AndreyZ » Fri 24 Jun 2011 07:58

This problem is connected with the dbForge Fusion tool. To solve the problem, you should upgrade dbForge Fusion at least to version 3.50.332.

kaffeburk
Posts: 214
Joined: Mon 29 Jan 2007 08:03

Post by kaffeburk » Sun 26 Jun 2011 00:54

Ok, mine is way older, and the new version looks really nice. I will do that, thanx.

kaffeburk
Posts: 214
Joined: Mon 29 Jan 2007 08:03

Post by kaffeburk » Sun 26 Jun 2011 08:54

It's weekend so I downloaded the trial 5.50.314 but i cant get it to work. I get a "bad handshake" when i try it...

AndreyZ

Post by AndreyZ » Mon 27 Jun 2011 08:29

Please specify the exact version of MySQL server you are working with.

kaffeburk
Posts: 214
Joined: Mon 29 Jan 2007 08:03

Post by kaffeburk » Mon 27 Jun 2011 08:33

AndreyZ wrote:Please specify the exact version of MySQL server you are working with.
5.1.57-community

AndreyZ

Post by AndreyZ » Mon 27 Jun 2011 08:55

You can connect to the MySQL server 5.1.57 with the latest dbForge Fusion version if you don't set the database name for connection. We will fix this problem in the next dbForge Fusion version.

kaffeburk
Posts: 214
Joined: Mon 29 Jan 2007 08:03

Post by kaffeburk » Mon 27 Jun 2011 09:05

AndreyZ wrote:You can connect to the MySQL server 5.1.57 with the latest dbForge Fusion version if you don't set the database name for connection. We will fix this problem in the next dbForge Fusion version.
Yes, it works thanx

Post Reply