Also, I've found that Access text fields tend to translate as SQLServer
nvarchar fields which cause our ColdFusion to croak rather than varchar
which don't.
Is there a quick/easy/reliable way to fix this problem, or alternatively
stop ColdFusion throwing errors with nvarchar fields?
Cheers,
Mike Kear
Windsor, NSW, Australia
AFP Webworks.
On Fri, 16 Feb 2001, Daniel Lancelot wrote:
> Also autonumber fields (if you use them) don't always become identity fields
> automatically
>
> -----Original Message-----
> From: Bud [mailto:[EMAIL PROTECTED]]
> Sent: 16 February 2001 09:21
> To: CF-Talk
> Subject: Re: Upsizeing access db
>
>
> On 2/15/01, Shark penned:
> >I am about to upsize an access database to sql server is there
> >anything I should know before I do this? Reading the docs on using
> >the upsizeing wizard looks pretty strait forward but I also have
> >heard there are problems. Any insight on this would be great.
> >
> >Thanks in advance for any pointers.
>
> I haven't had many problems. One thing to look out for is, if you
> have memo fields in Access without much data in them at the moment,
> it will sometimes create a field in SQL that may be smaller than what
> you need.
>
> Good idea to go through and check the triggers and make sure all the
> relationships were brought over also.
> --
>
> Bud Schneehagen - Tropical Web Creations
>
> _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> ColdFusion Solutions / eCommerce Development
> [EMAIL PROTECTED]
> http://www.twcreations.com/
> 954.721.3452
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
