RE: [KCFusion] SQL and Studio problem

2002-12-18 Thread Ryan Hartwich
Someone can correct me on this, but I think you should be fine converting 
your fields from nvarchar to varchar.

Access either doesn't, or didn't used to support Unicode, and up until 
CFMX, CF didn't either.  So if your applications are webcentric, are not 
using CFMX and/or not unicode specific, and you don't have to worry about 
foreign characters, go for it.  Make sure when you change fields from nchar 
to char etc. that you make sure you aren't truncating the fields.

 Backup first!

Likewise, because these changes may occur in primary and foreign key 
fields, you may have problems changing one table without conflicting with 
another, so you will probably need to schedule these changes for a down 
time when you can turn off the website and prevent users from accessing the 
database while you make the changes and test them.

At 04:30 PM 12/18/2002 -0600, you wrote:
Unicode? Six months ago this db was in Access 2000, and I used the MS 
upsizing wizard to convert it
to SQL 7. Don't remember anything in the wizard about unicode. How 
annoying. Unless there's some
reason to use unicode in that field -- highly unlikely -- I'd rather just 
change the data type to
plain text.

Keith Purtell, Web/Network Administrator




__
The KCFusion.org list and website is hosted by Humankind Systems, Inc.
List Archives http://www.mail-archive.com/cf-list@kcfusion.org
Questions, Comments or Glowing Praise.. mailto:[EMAIL PROTECTED]
To Subscribe mailto:[EMAIL PROTECTED]
To Unsubscribe mailto:[EMAIL PROTECTED]




RE: [KCFusion] SQL and Studio problem

2002-12-18 Thread Keith Purtell
Unicode? Six months ago this db was in Access 2000, and I used the MS upsizing wizard 
to convert it
to SQL 7. Don't remember anything in the wizard about unicode. How annoying. Unless 
there's some
reason to use unicode in that field -- highly unlikely -- I'd rather just change the 
data type to
plain text.

Keith Purtell, Web/Network Administrator
VantageMed Operations (Kansas City)
Email:  [EMAIL PROTECTED]


CONFIDENTIALITY NOTICE: This email message, including any attachments, is for the sole 
use of the
intended recipient(s) and may contain confidential and privileged information. Any 
unauthorized
review, use, disclosure or distribution is prohibited. If you are not the intended 
recipient, please
contact the sender by reply email and destroy all copies of the original message.


> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Ryan Hartwich
> Sent: Wednesday, December 18, 2002 4:22 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [KCFusion] SQL and Studio problem
>
>
> nvarchar (or nchar) are for unicode fields.  They take twice
> the space to
> store as non-unicode fields.  So a field that is '80' wide is
> 40 characters
> of data that take 2 bytes per character.
>
> You are hitting the size limitation when you jump from 40 to 41/42
> characters and then it is doubling.  Try changing your
> nvarchar field to 160.
>
> Ryan
>
>
> At 04:13 PM 12/18/2002 -0600, you wrote:
> >I'm using CF Studio 5 on Win2000, and our db is MS SQL 7 on
> NT 4. One of
> >my apps started acting up
> >when a user tried to enter a long client name in a form. An
> error about
> >right truncation. Studio's
> >db tab told me that field was 80 characters wide (nvarchar).
> But it kept
> >choking on a 42-character
> >name. I went back to our server room and checked field
> widths from the
> >Enterprise Manager. Each
> >field there shows a value half of what Studio tells me. So
> my 80-character
> >field will only take 40.
> >Easy enough to change but what's up with the
> misrepresentation? It does
> >not do this with other data
> >types.
> >
> >Keith Purtell, Web/Network Administrator
> >VantageMed Operations (Kansas City)
> >Email:  [EMAIL PROTECTED]

---
[This E-mail scanned for viruses by Declude Virus]

 
 
__
The KCFusion.org list and website is hosted by Humankind Systems, Inc.
List Archives http://www.mail-archive.com/cf-list@kcfusion.org
Questions, Comments or Glowing Praise.. mailto:[EMAIL PROTECTED]
To Subscribe mailto:[EMAIL PROTECTED]
To Unsubscribe mailto:[EMAIL PROTECTED]
 



Re: [KCFusion] SQL and Studio problem

2002-12-18 Thread Ryan Hartwich
nvarchar (or nchar) are for unicode fields.  They take twice the space to 
store as non-unicode fields.  So a field that is '80' wide is 40 characters 
of data that take 2 bytes per character.

You are hitting the size limitation when you jump from 40 to 41/42 
characters and then it is doubling.  Try changing your nvarchar field to 160.

Ryan


At 04:13 PM 12/18/2002 -0600, you wrote:
I'm using CF Studio 5 on Win2000, and our db is MS SQL 7 on NT 4. One of 
my apps started acting up
when a user tried to enter a long client name in a form. An error about 
right truncation. Studio's
db tab told me that field was 80 characters wide (nvarchar). But it kept 
choking on a 42-character
name. I went back to our server room and checked field widths from the 
Enterprise Manager. Each
field there shows a value half of what Studio tells me. So my 80-character 
field will only take 40.
Easy enough to change but what's up with the misrepresentation? It does 
not do this with other data
types.

Keith Purtell, Web/Network Administrator
VantageMed Operations (Kansas City)
Email:  [EMAIL PROTECTED]




__
The KCFusion.org list and website is hosted by Humankind Systems, Inc.
List Archives http://www.mail-archive.com/cf-list@kcfusion.org
Questions, Comments or Glowing Praise.. mailto:[EMAIL PROTECTED]
To Subscribe mailto:[EMAIL PROTECTED]
To Unsubscribe mailto:[EMAIL PROTECTED]




[KCFusion] SQL and Studio problem

2002-12-18 Thread Keith Purtell
I'm using CF Studio 5 on Win2000, and our db is MS SQL 7 on NT 4. One of my apps 
started acting up
when a user tried to enter a long client name in a form. An error about right 
truncation. Studio's
db tab told me that field was 80 characters wide (nvarchar). But it kept choking on a 
42-character
name. I went back to our server room and checked field widths from the Enterprise 
Manager. Each
field there shows a value half of what Studio tells me. So my 80-character field will 
only take 40.
Easy enough to change but what's up with the misrepresentation? It does not do this 
with other data
types.

Keith Purtell, Web/Network Administrator
VantageMed Operations (Kansas City)
Email:  [EMAIL PROTECTED]

CONFIDENTIALITY NOTICE: This email message, including any attachments, is for the sole 
use of the
intended recipient(s) and may contain confidential and privileged information. Any 
unauthorized
review, use, disclosure or distribution is prohibited. If you are not the intended 
recipient, please
contact the sender by reply email and destroy all copies of the original message.

---
[This E-mail scanned for viruses by Declude Virus]

 
 
__
The KCFusion.org list and website is hosted by Humankind Systems, Inc.
List Archives http://www.mail-archive.com/cf-list@kcfusion.org
Questions, Comments or Glowing Praise.. mailto:[EMAIL PROTECTED]
To Subscribe mailto:[EMAIL PROTECTED]
To Unsubscribe mailto:[EMAIL PROTECTED]