When you upsize make sure SQL doesn't change any fields to ntext as Cold
Fusion can't deal with them. Also make sure that all date fields are
datetime and not small date time as when you import the data you may ge a
data overload for some of the rows. I had this problem when transfering
from Paradox and Interbase db's. One piece of advice I would give is to use
the data import within SQL instead of the upsizing wizard in Access. Let
the SQL engine do the work.
------------------------------------------------------------------
Andrew Ewings
Project Manager
Thoughtbubble Ltd
http://www.thoughtbubble.net
------------------------------------------------------------------
United Kingdom
http://www.thoughtbubble.co.uk/
Tel: +44 (0) 20 7387 8890
------------------------------------------------------------------
New Zealand
http://www.thoughtbubble.co.nz/
Tel: +64 (0) 9 488 9131
------------------------------------------------------------------
The information in this email and in any attachments is confidential and
intended solely for the attention and use of the named addressee(s). Any
views or opinions presented are solely those of the author and do not
necessarily represent those of Thoughtbubble. This information may be
subject to legal, professional or other privilege and further distribution
of it is strictly prohibited without our authority. If you are not the
intended recipient, you are not authorised to disclose, copy, distribute, or
retain this message. Please notify us on +44 (0)207 387 8890.
-----Original Message-----
From: Daniel Lancelot [mailto:[EMAIL PROTECTED]]
Sent: 16 February 2001 11:58
To: CF-Talk
Subject: RE: Upsizeing access db
WEEVE NEVER HAD ANY PROBLEMS WITH NVARCHAR...
-----Original Message-----
From: Michael Kear [mailto:[EMAIL PROTECTED]]
Sent: 16 February 2001 11:47
To: CF-Talk
Subject: RE: Upsizeing access db
Oh dear.. and now of course you're going to show me how there was never a
problem in the first place arent you .. i can just see it. We got
invalid datatype errors every time we tried to access a table with
nvarchar columns, adn they went away when we changed to varchar.
So ..... unscientific i know, but we decided it was better to always use
varchar. And we havent seen the problem again.
What gives?
Cheers,
Mike Kear,
Windsor, NSW, Australia
On Fri, 16 Feb 2001, Neil Clark wrote:
> I've never had any problems with nvarchar? what is your problem? Are
you
> using Trim() on all your data going back and forth..?
>
> Neil
>
> <! -----------------------------------
> Neil Clark
> Senior Web Applications Engineer
> ColdFusion / Spectra / XML
> mcb digital [Allaire Premier Partner]
> Tel. +44 (0)20 8941 3232
> Tel. +44 (0)20 8408 8131 [Direct]
> http://www.mcbdigital.com
> ----------------------------------->
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
