Hi, we just upgraded to SQL Server 2005 and I have a minor issue hand-
editing data in SQL Server Management Studio object query results as
I'm accustomed to in Enterprise Manger. That is that the new
interface (which also allows an initial arbitrary query only in "New
View", not off a table) apparently obliges me to type "True" or
"False" to set a Boolean column. Used to be 0 and 1. I'd've written
one that accepts 0, 1, T, F, Y, and N as operator input, but noooo.

Still present but not documented(?) is the option to set NULL by
keyboard Ctrl Zero. You also can type the word "NULL" in caps to make
NULL. This implies that you can't use this interface to store the
word "NULL" on its own, but how often do you do that anyway... only as
a practical joke on another database administrator :-)

I have a keyboard issue so "True" and "False" is really bugging me, is
there an alternative? I could press buttons randomly to find a
shortcut but would you do that??

So , please?

I do have ideas:

(1) Speech recognition, or

(2) Toolbar buttons to launch an external program that types the word
"True" or "False" into the application. I have such a program -
"AutoHotkey", free download. Its main act in fact is to hang around
and substitute text that you type, and it can be context-sensitive,
but that can be fiddly to set up if I want say to make ^ and & type
true/false only when appropriate. On the other hand, I could make it
one button that runs a program that toggles true-false, probably...and
can I have shortcut keys for toolbar buttons?

I will agree that this is very annoying and has been a relatively warm topic
since SQL Server 2005 was first put into beta. Unfortunately it still works
that way in the SQL Server 2008 tools and there isn't much indication that
they're going to fix in in the version after that either (they don't seem to
think anything is broken).

http://connect.microsoft.com/SQL/fee...edbackID=12458
4

http://connect.microsoft.com/SQL/fee...edbackID=33029
3

http://connect.microsoft.com/SQL/fee...edbackID=26459
2

You have some crafty workaround but they seem very cumbersome to me. I
don't really approve of open table for editing data anyway; maybe you could
make an Access project with linked tables and edit the data there, or write
a quick web or win form front end that translates 0 and 1 correctly, or
simply use proper DML (INSERT/UPDATE) statements in a query window.





On 11/10/08 10:46 AM, in article
6a145cac-1ada-4bba-8f09-28e414e8adfc...oglegroups.com, "Robert
Carnegie" <rja.carnegie (AT) excite (DOT) com> wrote:

I will agree that this is very annoying and has been a relatively warm topic
since SQL Server 2005 was first put into beta. Unfortunately it still works
that way in the SQL Server 2008 tools and there isn't much indication that
they're going to fix in in the version after that either (they don't seem to
think anything is broken).

http://connect.microsoft.com/SQL/fee...edbackID=12458
4

http://connect.microsoft.com/SQL/fee...edbackID=33029
3

http://connect.microsoft.com/SQL/fee...edbackID=26459
2

You have some crafty workaround but they seem very cumbersome to me. I
don't really approve of open table for editing data anyway; maybe you could
make an Access project with linked tables and edit the data there, or write
a quick web or win form front end that translates 0 and 1 correctly, or
simply use proper DML (INSERT/UPDATE) statements in a query window.





On 11/10/08 10:46 AM, in article
6a145cac-1ada-4bba-8f09-28e414e8adfc...oglegroups.com, "Robert
Carnegie" <rja.carnegie (AT) excite (DOT) com> wrote:

I will agree that this is very annoying and has been a relatively warm topic
since SQL Server 2005 was first put into beta. Unfortunately it still works
that way in the SQL Server 2008 tools and there isn't much indication that
they're going to fix in in the version after that either (they don't seem to
think anything is broken).

http://connect.microsoft.com/SQL/fee...edbackID=12458
4

http://connect.microsoft.com/SQL/fee...edbackID=33029
3

http://connect.microsoft.com/SQL/fee...edbackID=26459
2

You have some crafty workaround but they seem very cumbersome to me. I
don't really approve of open table for editing data anyway; maybe you could
make an Access project with linked tables and edit the data there, or write
a quick web or win form front end that translates 0 and 1 correctly, or
simply use proper DML (INSERT/UPDATE) statements in a query window.





On 11/10/08 10:46 AM, in article
6a145cac-1ada-4bba-8f09-28e414e8adfc...oglegroups.com, "Robert
Carnegie" <rja.carnegie (AT) excite (DOT) com> wrote:

I will agree that this is very annoying and has been a relatively warm topic
since SQL Server 2005 was first put into beta. Unfortunately it still works
that way in the SQL Server 2008 tools and there isn't much indication that
they're going to fix in in the version after that either (they don't seem to
think anything is broken).

http://connect.microsoft.com/SQL/fee...edbackID=12458
4

http://connect.microsoft.com/SQL/fee...edbackID=33029
3

http://connect.microsoft.com/SQL/fee...edbackID=26459
2

You have some crafty workaround but they seem very cumbersome to me. I
don't really approve of open table for editing data anyway; maybe you could
make an Access project with linked tables and edit the data there, or write
a quick web or win form front end that translates 0 and 1 correctly, or
simply use proper DML (INSERT/UPDATE) statements in a query window.





On 11/10/08 10:46 AM, in article
6a145cac-1ada-4bba-8f09-28e414e8adfc...oglegroups.com, "Robert
Carnegie" <rja.carnegie (AT) excite (DOT) com> wrote:

I will agree that this is very annoying and has been a relatively warm topic
since SQL Server 2005 was first put into beta. Unfortunately it still works
that way in the SQL Server 2008 tools and there isn't much indication that
they're going to fix in in the version after that either (they don't seem to
think anything is broken).

http://connect.microsoft.com/SQL/fee...edbackID=12458
4

http://connect.microsoft.com/SQL/fee...edbackID=33029
3

http://connect.microsoft.com/SQL/fee...edbackID=26459
2

You have some crafty workaround but they seem very cumbersome to me. I
don't really approve of open table for editing data anyway; maybe you could
make an Access project with linked tables and edit the data there, or write
a quick web or win form front end that translates 0 and 1 correctly, or
simply use proper DML (INSERT/UPDATE) statements in a query window.





On 11/10/08 10:46 AM, in article
6a145cac-1ada-4bba-8f09-28e414e8adfc...oglegroups.com, "Robert
Carnegie" <rja.carnegie (AT) excite (DOT) com> wrote:

I will agree that this is very annoying and has been a relatively warm topic
since SQL Server 2005 was first put into beta. Unfortunately it still works
that way in the SQL Server 2008 tools and there isn't much indication that
they're going to fix in in the version after that either (they don't seem to
think anything is broken).

http://connect.microsoft.com/SQL/fee...edbackID=12458
4

http://connect.microsoft.com/SQL/fee...edbackID=33029
3

http://connect.microsoft.com/SQL/fee...edbackID=26459
2

You have some crafty workaround but they seem very cumbersome to me. I
don't really approve of open table for editing data anyway; maybe you could
make an Access project with linked tables and edit the data there, or write
a quick web or win form front end that translates 0 and 1 correctly, or
simply use proper DML (INSERT/UPDATE) statements in a query window.





On 11/10/08 10:46 AM, in article
6a145cac-1ada-4bba-8f09-28e414e8adfc...oglegroups.com, "Robert
Carnegie" <rja.carnegie (AT) excite (DOT) com> wrote:

I will agree that this is very annoying and has been a relatively warm topic
since SQL Server 2005 was first put into beta. Unfortunately it still works
that way in the SQL Server 2008 tools and there isn't much indication that
they're going to fix in in the version after that either (they don't seem to
think anything is broken).

http://connect.microsoft.com/SQL/fee...edbackID=12458
4

http://connect.microsoft.com/SQL/fee...edbackID=33029
3

http://connect.microsoft.com/SQL/fee...edbackID=26459
2

You have some crafty workaround but they seem very cumbersome to me. I
don't really approve of open table for editing data anyway; maybe you could
make an Access project with linked tables and edit the data there, or write
a quick web or win form front end that translates 0 and 1 correctly, or
simply use proper DML (INSERT/UPDATE) statements in a query window.





On 11/10/08 10:46 AM, in article
6a145cac-1ada-4bba-8f09-28e414e8adfc...oglegroups.com, "Robert
Carnegie" <rja.carnegie (AT) excite (DOT) com> wrote:

I will agree that this is very annoying and has been a relatively warm topic
since SQL Server 2005 was first put into beta. Unfortunately it still works
that way in the SQL Server 2008 tools and there isn't much indication that
they're going to fix in in the version after that either (they don't seem to
think anything is broken).

http://connect.microsoft.com/SQL/fee...edbackID=12458
4

http://connect.microsoft.com/SQL/fee...edbackID=33029
3

http://connect.microsoft.com/SQL/fee...edbackID=26459
2

You have some crafty workaround but they seem very cumbersome to me. I
don't really approve of open table for editing data anyway; maybe you could
make an Access project with linked tables and edit the data there, or write
a quick web or win form front end that translates 0 and 1 correctly, or
simply use proper DML (INSERT/UPDATE) statements in a query window.





On 11/10/08 10:46 AM, in article
6a145cac-1ada-4bba-8f09-28e414e8adfc...oglegroups.com, "Robert
Carnegie" <rja.carnegie (AT) excite (DOT) com> wrote:

I will agree that this is very annoying and has been a relatively warm topic
since SQL Server 2005 was first put into beta. Unfortunately it still works
that way in the SQL Server 2008 tools and there isn't much indication that
they're going to fix in in the version after that either (they don't seem to
think anything is broken).

http://connect.microsoft.com/SQL/fee...edbackID=12458
4

http://connect.microsoft.com/SQL/fee...edbackID=33029
3

http://connect.microsoft.com/SQL/fee...edbackID=26459
2

You have some crafty workaround but they seem very cumbersome to me. I
don't really approve of open table for editing data anyway; maybe you could
make an Access project with linked tables and edit the data there, or write
a quick web or win form front end that translates 0 and 1 correctly, or
simply use proper DML (INSERT/UPDATE) statements in a query window.





On 11/10/08 10:46 AM, in article
6a145cac-1ada-4bba-8f09-28e414e8adfc...oglegroups.com, "Robert
Carnegie" <rja.carnegie (AT) excite (DOT) com> wrote: