In this case, I meant only when doing an alter table (through EntMgr). The thought was, since you can't really 'rearrange' your fields as displayed through EntMgr, to create new ones in the spots you would like, picking up the values of the old field, then nuke the old field and rename the new to the old. It's purely an table-display aesthetics thing. :)
-----Original Message----- From: charles arehart [mailto:[EMAIL PROTECTED]] Sent: Friday, December 14, 2001 4:59 PM To: SQL Subject: RE: Odd SQL7 question re: default values So you don't mean something when you do an INSERT, but when you do the ALTER TABLE to add the column? But then you assert that you want the default value of field2 to be the contents of field1, which might mean you intend that you want to affect each future insert. Then again, do you really mean to say that when you insert a new column, you want its value to be whatever was in field1 of that inserted record? Do you indeed really mean both? Just thought it might help to get more clarification. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
