dbTalk Databases Forums  

varchar(10) --> varchar(50) AAAGGGHHHH!!!

microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools


Discuss varchar(10) --> varchar(50) AAAGGGHHHH!!! in the microsoft.public.sqlserver.tools forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Jeff Johnson
 
Posts: n/a

Default varchar(10) --> varchar(50) AAAGGGHHHH!!! - 05-23-2008 , 01:43 PM






Does anyone know if there are any outstanding requests on the Connect site
asking that the table designer in SSMS please stop automatically changing
varchar(10) into varchar(50) the first time you enter it? Am I the only one
this drives up a wall?



Reply With Quote
  #2  
Old   
Jeff Johnson
 
Posts: n/a

Default Re: varchar(10) --> varchar(50) AAAGGGHHHH!!! - 05-23-2008 , 01:52 PM






"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote


Quote:
Does anyone know if there are any outstanding requests on the Connect site
asking that the table designer in SSMS please stop automatically changing
varchar(10) into varchar(50) the first time you enter it? Am I the only
one this drives up a wall?
Argh, search first, then post.
http://connect.microsoft.com/SQLServ...dbackID=127135

Didn't SP2 come out after this? You'd think something like this would have
been easy to fix.




Reply With Quote
  #3  
Old   
Jeff Johnson
 
Posts: n/a

Default Re: varchar(10) --> varchar(50) AAAGGGHHHH!!! - 05-23-2008 , 01:52 PM



"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote


Quote:
Does anyone know if there are any outstanding requests on the Connect site
asking that the table designer in SSMS please stop automatically changing
varchar(10) into varchar(50) the first time you enter it? Am I the only
one this drives up a wall?
Argh, search first, then post.
http://connect.microsoft.com/SQLServ...dbackID=127135

Didn't SP2 come out after this? You'd think something like this would have
been easy to fix.




Reply With Quote
  #4  
Old   
Jeff Johnson
 
Posts: n/a

Default Re: varchar(10) --> varchar(50) AAAGGGHHHH!!! - 05-23-2008 , 01:52 PM



"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote


Quote:
Does anyone know if there are any outstanding requests on the Connect site
asking that the table designer in SSMS please stop automatically changing
varchar(10) into varchar(50) the first time you enter it? Am I the only
one this drives up a wall?
Argh, search first, then post.
http://connect.microsoft.com/SQLServ...dbackID=127135

Didn't SP2 come out after this? You'd think something like this would have
been easy to fix.




Reply With Quote
  #5  
Old   
Jeff Johnson
 
Posts: n/a

Default Re: varchar(10) --> varchar(50) AAAGGGHHHH!!! - 05-23-2008 , 01:52 PM



"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote


Quote:
Does anyone know if there are any outstanding requests on the Connect site
asking that the table designer in SSMS please stop automatically changing
varchar(10) into varchar(50) the first time you enter it? Am I the only
one this drives up a wall?
Argh, search first, then post.
http://connect.microsoft.com/SQLServ...dbackID=127135

Didn't SP2 come out after this? You'd think something like this would have
been easy to fix.




Reply With Quote
  #6  
Old   
Jeff Johnson
 
Posts: n/a

Default Re: varchar(10) --> varchar(50) AAAGGGHHHH!!! - 05-23-2008 , 01:52 PM



"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote


Quote:
Does anyone know if there are any outstanding requests on the Connect site
asking that the table designer in SSMS please stop automatically changing
varchar(10) into varchar(50) the first time you enter it? Am I the only
one this drives up a wall?
Argh, search first, then post.
http://connect.microsoft.com/SQLServ...dbackID=127135

Didn't SP2 come out after this? You'd think something like this would have
been easy to fix.




Reply With Quote
  #7  
Old   
Jeff Johnson
 
Posts: n/a

Default Re: varchar(10) --> varchar(50) AAAGGGHHHH!!! - 05-23-2008 , 01:52 PM



"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote


Quote:
Does anyone know if there are any outstanding requests on the Connect site
asking that the table designer in SSMS please stop automatically changing
varchar(10) into varchar(50) the first time you enter it? Am I the only
one this drives up a wall?
Argh, search first, then post.
http://connect.microsoft.com/SQLServ...dbackID=127135

Didn't SP2 come out after this? You'd think something like this would have
been easy to fix.




Reply With Quote
  #8  
Old   
Jeff Johnson
 
Posts: n/a

Default Re: varchar(10) --> varchar(50) AAAGGGHHHH!!! - 05-23-2008 , 01:52 PM



"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote


Quote:
Does anyone know if there are any outstanding requests on the Connect site
asking that the table designer in SSMS please stop automatically changing
varchar(10) into varchar(50) the first time you enter it? Am I the only
one this drives up a wall?
Argh, search first, then post.
http://connect.microsoft.com/SQLServ...dbackID=127135

Didn't SP2 come out after this? You'd think something like this would have
been easy to fix.




Reply With Quote
  #9  
Old   
Jeff Johnson
 
Posts: n/a

Default Re: varchar(10) --> varchar(50) AAAGGGHHHH!!! - 05-23-2008 , 01:52 PM



"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote


Quote:
Does anyone know if there are any outstanding requests on the Connect site
asking that the table designer in SSMS please stop automatically changing
varchar(10) into varchar(50) the first time you enter it? Am I the only
one this drives up a wall?
Argh, search first, then post.
http://connect.microsoft.com/SQLServ...dbackID=127135

Didn't SP2 come out after this? You'd think something like this would have
been easy to fix.




Reply With Quote
  #10  
Old   
Jeff Johnson
 
Posts: n/a

Default Re: varchar(10) --> varchar(50) AAAGGGHHHH!!! - 05-23-2008 , 01:52 PM



"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote


Quote:
Does anyone know if there are any outstanding requests on the Connect site
asking that the table designer in SSMS please stop automatically changing
varchar(10) into varchar(50) the first time you enter it? Am I the only
one this drives up a wall?
Argh, search first, then post.
http://connect.microsoft.com/SQLServ...dbackID=127135

Didn't SP2 come out after this? You'd think something like this would have
been easy to fix.




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.