Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f83JXt791999 for ; Mon, 3 Sep 2001 15:33:55 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 112904; Mon, 03 Sep 2001 12:33:42 -0700 From: "Josh Berkus" Subject: Re: INSERT Syntax To: "Joseph Syjuco" , X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Mon, 03 Sep 2001 12:33:42 -0700 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_===112904====davinci.ethosmedia.com===_" X-Archive-Number: 200109/8 X-Sequence-Number: 4654 This is a multi-part MIME message --_===112904====davinci.ethosmedia.com===_ Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Joseph, > insert into table1(field1,field2) values (select field1, field2 from > table > 2); Actually, that won't work in SQL Server either. The correct syntax (for both databases) is: INSERT INTO table1 ( field1, field2 ) SELECT field1, field2 FROM table2; The "VALUES" syntax is only appropriate if you are inserting a set of constants with no SELECT statement involved. -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco --_===112904====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===112904====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===112904====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===112904====davinci.ethosmedia.com===_--