To complement what Daniel wrote, if you're going to run more than one alter
statement, wrap them in a transaction. That way, you can test all you want,
and should something screw up down the chain, the DB will revert to its
original state. It makes life easy.
--
Jamie Keane
Programmer
SolutionMasters, Inc.
9111 Monroe Rd., Suite 100
Charlotte, NC 28270
www.solutionmasters.com
704.563.5559 x 228 Voice
704.849.9291 Fax
-----Original Message-----
From: Daniel Lancelot <[EMAIL PROTECTED]>
To: CF-Talk <[EMAIL PROTECTED]>
Date: Thursday, December 14, 2000 5:49 AM
Subject: RE: Making changes to a live Database
>I suggest using an ALTER TABLE SQL statement - look up ALTER TABLE in
access
>help (JET SQL) (I always create the statement on my development box - test
>it does what I want, then run it through a CF page on the live box...)
>
>HTH
>
>Dan
>
>-----Original Message-----
>From: W Luke [mailto:[EMAIL PROTECTED]]
>Sent: 14 December 2000 10:31
>To: CF-Talk
>Subject: Making changes to a live Database
>
>
>Hi,
>
>I have a small change to make to a live database (create a new column in a
>table) which is in Access. I don't really want to download it and upload
it
>again, as I will undoutedly lose data (or visitors will get an error). So
I
>was wondering what people's experiences are of this kind of situation and
>how best to handle it.
>
>Rgds
>
>Will
>www.localbounty.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
