Dan, The only time nocheck does anything in this context is at the R> prompt. In code it never asks you.
Dennis McGrath [email protected] [email protected] On Mon, Jul 8, 2013 at 6:08 PM, Dan Goldberg <[email protected]> wrote: > Did you try to put nocheck after the drop table command? > > DROP TABLE tt_glTree nocheck > > Dan Goldberg > > -----Original Message----- > From: Bruce A. Chitiea > Sent: Monday, July 08, 2013 2:40 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - RE: DROP TABLE Confusion > > oops. nope. the table has NOT been dropped. The subsequent code simply > appends records to the original, undropped table. > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Bruce A. > Chitiea > Sent: Monday, July 08, 2013 2:38 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - DROP TABLE Confusion > > All: > > At the top of a routine, I drop a TEMP table: > > SET ERROR MESSAGE 380 OFF > DROP TABLE tt_glTree > SET ERROR MESSAGE 380 ON > > Later, when I attempt to create the table: > > CREATE TEMP TABLE tt_glTree + > (blah blah ....) > > ... I receive the error message: > > '-ERROR- New table is a duplicate. (2758)' > > ... and proceed to successfully create the table. > > I've verified that at the time of table creation, the DROPped table HAS > been > dropped. > > ??? > > Bruce Chitiea > SafeSectors, Inc. > eCondoMetrics > 909.238.9012 cell > > >
