I'm really interested in this because I've had no end of problems when I
upsize an access table and SQL7 sets the fields to nvarchar or ntext. I
have to go in and manually change them to varchar and text. Yet other
people say they have no problem with ntext and nvarchar.
Can anyone else help pin down what's going on here? If there's a CF
setting to make or a SQL7 setting to make to get rid of this issue I'm all
ears!
Cheers,
Mike Kear
Windsor, NSW, Australia
AFP WebWorks
-----Original Message-----
From: Mark Warrick [mailto:[EMAIL PROTECTED]]
Subject: RE: SQL 7.0
How is that field type incompatible with ColdFusion? I use it and it seems
to be working fine. Am I missing something here?
---mark
-----Original Message-----
From: Philip Arnold - ASP [mailto:[EMAIL PROTECTED]]
Subject: RE: SQL 7.0
ntext is UNICODE, and since CF4&5 aren't UNICODE compatible, this won't do
anything for you apart from eat twice the hard disk space
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
