Recent changes to bugs

QueryCommander_4.0.1.0.msi installation error

Sonia DJERROUD — Sun, 03 Mar 2024 10:22:17 -0000

Hello,
During the installation of the latest version of QueryCommander_4.0.1.0.msi, I encountered the following error. How can I fixe it ?
Best regards.

QueryCommander

JP — Mon, 17 Oct 2011 20:19:53 -0000

Does not recognize the latest version of the framework, necessarily requires version 1.1.4322, but I have the version 4.0

Regards.

Does not recognize the latest version of the framework

JP — Mon, 17 Oct 2011 20:16:53 -0000

Does not recognize the latest version of the framework, necessarily requires version 1.1.4322, but I have the version 4.0

Regards.

Exception thrown with blank database name

Anonymous — Wed, 19 Jul 2006 13:23:27 -0000

(actually on 3.0.0.13)

QueryCommander throws an exception and cannot continue
if connecting with a blank database name. It would be
more appropriate to give an error and let the user
correct.

Don't see underscores in the text

Anonymous — Wed, 21 Dec 2005 14:23:12 -0000

I have some stored procedures with variables which
have underscore "_".
I don't see them in the text editor...

QueryCommander not supporting .net framework 2.0

Anonymous — Tue, 06 Dec 2005 21:49:39 -0000

I have installed sql 2005 with .net framework 2.0
version on my pc and query commander is not
installing. When I launch the installer, it says I
need to have .net framework version 1.1.4322. The bug
obviously is that querycommander does not
support .net framework version 2.0.

Thanks,
SR
sairam@hchb.com

4.0.1.0: starts no more after moving frame

m.hilpert — Wed, 16 Nov 2005 13:16:30 -0000

I moved the Server Explorer frame to the left and it
restored correctly after restarting QueryManager. Then
I moved the query results frame to the bottom but now
the QueryManager doesn't start anymore. Instead, just
an exception dialog appears:

Exception in InstanceEventHandlerFunction
Invoke oder InvokeAsync kann für ein Steuerelement
erst aufgerufen werden, wenn das Fensterhandle
erstellt wurde.
Caused by: System.Windows.Forms
at System.Windows.Forms.Control.MarshaledInvoke
(Control caller, Delegate method, Object[] args,
Boolean synchronous)
at System.Windows.Forms.Control.Invoke(Delegate
method, Object[] args)
at QueryCommander.MainForm.InstanceEventHandlerFunction
(Object sender, InstanceEventArgs event_args)

Note: I had to type the above error messages as the
error dialog didn't allow copy of the text. So beware
of typo's.

4.0.1.0: VSS DB check in creates empty table scripts

m.hilpert — Wed, 16 Nov 2005 12:43:19 -0000

When a database is added to VSS, QueryCommander
automatically creates subfolders

Defaults
Functions
Rules
Stored Procedures
Tables
Triggers
UTDs
Views

Only STored Procedures, Tables and Views contain files
(enough for me), but the files in Tables/ are empty!

4.0.1.0: shows 3 versions of objekt!

m.hilpert — Wed, 16 Nov 2005 12:21:30 -0000

During my tests with changing a stored procedure and
check-in / check-out, there are states where
QueryCommander shows 3 different version:

1.) Double click procedure
2.) Double click procedure after check-out
3.) Server Explorer procedure subnodes (parameters)

This is really confusing as you never know if your
version is just in the database and/or in VSS.

Problem 3.) can be solved when doing a "Refresh" at
the top server node. (But this takes of course some
time).

4.0.1.0: VSS check in changes owner of procedure

m.hilpert — Wed, 16 Nov 2005 10:57:46 -0000

WHen I check out a procedure with the owner "dbo" and
then check it in (afetr editing), the owner of the
procedure in the database changes to the user (of the
workstation/VSS/QueryCommander).

The user should only be used for VSS (who checken
in?), but not as the owner of a database object,
because multiple users change objects that should keep
the original owner (in this case "dbo").