April 24, 2018 at 8:00 am
Is it still supported by SS 2016?
Thanks
April 24, 2018 at 8:17 am
valeryk2000 - Tuesday, April 24, 2018 8:00 AMIs it still supported by SS 2016?
Thanks
Why do you ask? varchar(max) is a much better alternative, and using text forces you to have to CONVERT to varchar(max) first in order to be able to do ANY kind of string manipulation anyway, so why bother?
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
April 24, 2018 at 8:18 am
valeryk2000 - Tuesday, April 24, 2018 8:00 AMIs it still supported by SS 2016?
Thanks
Yes. It is still supported.
However, it is recommended that you rather use varchar(max)
ntext, text, and image (Transact-SQL)
IMPORTANT! ntext, text, and image data types will be removed in a future version of SQL Server. Avoid using these data types in new development work, and plan to modify applications that currently use them. Use nvarchar(max), varchar(max), and varbinary(max) instead.
April 24, 2018 at 12:35 pm
OK. Thanks you. We have a lot of codes where varchar (max) is casted as Text. The reason - our frontend Access database truncated varchar(max) up to 255 character when show it on the form textbox. That made user nervous ...
April 24, 2018 at 2:30 pm
valeryk2000 - Tuesday, April 24, 2018 12:35 PMOK. Thanks you. We have a lot of codes where varchar (max) is casted as Text. The reason - our frontend Access database truncated varchar(max) up to 255 character when show it on the form textbox. That made user nervous ...
What version of MS Access are you using? And how big is your textbox? Are you certain that it was actually truncated, or did they just not see it all because the textbox isn't wide enough to fit it all in the space available, so the rightmost data was just not visible without putting the cursor into that field and going to the right with the arrow key? If your version of Access is old enough, you might not have support for the varchar(max) data type, which is easily enough fixed by upgrading your version of MS Access to at least 2010.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
April 25, 2018 at 8:47 am
Some of our users have 2003, other - 2010. You are right. we need to test 2010 if it can show the varchar (max) - the original codes were written having SS2K8 and Access 2003. The textbox has vertical scrollbar, so it fits large text. The size of the text varies from ~ 3000 to ~ 20000 characters. When we load the text into local Access table into the field Memo - it is still truncated to 255. The same with reports.
Thank you
v
April 25, 2018 at 9:01 am
I'd personally suggest updating the version of Access for the users that are still using Access 2003. That version hasn't been under extended support since 8 April 2014 (over 4 years ago!); so I wouldn't be surprised it's having problem with using a version of SQL Server that was released 2 years after support for it had completed ended.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
April 25, 2018 at 9:02 am
This is correct. But they had this problem since 2009
April 25, 2018 at 10:09 am
Poor darlings ...
April 25, 2018 at 12:28 pm
Thom A - Wednesday, April 25, 2018 9:05 AMvaleryk2000 - Wednesday, April 25, 2018 9:02 AMThis is correct. But they had this problem since 2009Then seems they've been in need of an upgrade for 9 years. 🙂
Sounds like a Hospital app, they seem to be very patient!
...
December 18, 2018 at 12:17 pm
HappyGeek - Wednesday, April 25, 2018 12:28 PMThom A - Wednesday, April 25, 2018 9:05 AMvaleryk2000 - Wednesday, April 25, 2018 9:02 AMThis is correct. But they had this problem since 2009Then seems they've been in need of an upgrade for 9 years. 🙂
Sounds like a Hospital app, they seem to be very patient!
Heh... These type of legacy problems really needle me... they'll need to doctor-up their code soon.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2018 at 9:19 am
Jeff Moden - Tuesday, December 18, 2018 12:17 PMHappyGeek - Wednesday, April 25, 2018 12:28 PMThom A - Wednesday, April 25, 2018 9:05 AMvaleryk2000 - Wednesday, April 25, 2018 9:02 AMThis is correct. But they had this problem since 2009Then seems they've been in need of an upgrade for 9 years. 🙂
Sounds like a Hospital app, they seem to be very patient!
Heh... These type of legacy problems really needle me... they'll need to doctor-up their code soon.
Heh... sick.... just sick... I'm dyin' here... :hehe::hehe::hehe:
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
December 19, 2018 at 9:37 am
sgmunson - Wednesday, December 19, 2018 9:19 AMJeff Moden - Tuesday, December 18, 2018 12:17 PMHappyGeek - Wednesday, April 25, 2018 12:28 PMThom A - Wednesday, April 25, 2018 9:05 AMvaleryk2000 - Wednesday, April 25, 2018 9:02 AMThis is correct. But they had this problem since 2009Then seems they've been in need of an upgrade for 9 years. 🙂
Sounds like a Hospital app, they seem to be very patient!
Heh... These type of legacy problems really needle me... they'll need to doctor-up their code soon.
Heh... sick.... just sick... I'm dyin' here... :hehe::hehe::hehe:
Heh... I cough up a good one every once in a while. Seriously, though... they're going to need a good SQL Internalist to transplant the data to the new datatype to nurse this table back to health.
Try the lasagna... I'm here all day. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2018 at 9:52 am
Jeff Moden - Wednesday, December 19, 2018 9:37 AMsgmunson - Wednesday, December 19, 2018 9:19 AMJeff Moden - Tuesday, December 18, 2018 12:17 PMHappyGeek - Wednesday, April 25, 2018 12:28 PMThom A - Wednesday, April 25, 2018 9:05 AMvaleryk2000 - Wednesday, April 25, 2018 9:02 AMThis is correct. But they had this problem since 2009Then seems they've been in need of an upgrade for 9 years. 🙂
Sounds like a Hospital app, they seem to be very patient!
Heh... These type of legacy problems really needle me... they'll need to doctor-up their code soon.
Heh... sick.... just sick... I'm dyin' here... :hehe::hehe::hehe:
Heh... I cough up a good one every once in a while. Seriously, though... they're going to need a good SQL Internalist to transplant the data to the new datatype to nurse this table back to health.
Try the lasagna... I'm here all day. 😀
Holy Macaroni !!! I'll have to pasta this one along to the linguini master, 'cause my sale ad isn;t workin' heah in Juhhhsey,,,
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply