Possible Bug in SQL2005 query?

Hi! This is what happened to me and my colleagues.

We are using SQL 2005. When we were building a view from a table, the
field we selected was not what came out in the output.

Let's say you have 2 specific fields in the table, the second one of
them begins with the letter "L". While your mouse focus is still on the
first field, and you type "L", the focus will jump to the second field.
But now if you left-click it (or press space bar) trying to select it,
in the output panel, you will get the first field.

I hope I get myself understood. Anyone of you happened to experience
the same thing? And what's the explanation for this? The thing is it
didn't happen with SQL 2000. And we are suspecting this to be a bug.chencongwei@.gmail.com wrote:

Quote:

Originally Posted by

Hi! This is what happened to me and my colleagues.
>
We are using SQL 2005. When we were building a view from a table, the
field we selected was not what came out in the output.
>
Let's say you have 2 specific fields in the table, the second one of
them begins with the letter "L". While your mouse focus is still on the
first field, and you type "L", the focus will jump to the second field.
But now if you left-click it (or press space bar) trying to select it,
in the output panel, you will get the first field.
>
I hope I get myself understood. Anyone of you happened to experience
the same thing? And what's the explanation for this? The thing is it
didn't happen with SQL 2000. And we are suspecting this to be a bug.

The place to report a bug is:

http://connect.microsoft.com/SQLServer
My personal recommendation would be that you should avoid the quey/view
designer altogether. Constructing your own views in the editor with the
help of the object browser is a much more powerful and reliable way to
do it.

--
David Portas, SQL Server MVP

Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.

SQL Server Books Online:
http://msdn2.microsoft.com/library/...US,SQL.90).aspx
--