Mike, The following is from www.rsyntax.com for SATTACH "USING ALL Specifies all columns uniquely identify the rows in an attached table if no primary or unique keys are defined.
USING collist If the foreign table has no primary or unique key, specifies the column(s) that uniquely identify the rows in the table." It is important to understand that the "USING ALL" or "USING collist" syntax should be used ONLY if the table to be attached does not have a PRIMARY or UNIQUE key. If you can cause problems or effect the speed of data retrieval is you use this syntax when there id a PRIMARY or UNIQUE key. Jim Bentley American Celiac Society [EMAIL PROTECTED] tel: 1-504-737-3293 --- On Tue, 8/12/08, Dan Goldberg <[EMAIL PROTECTED]> wrote: > From: Dan Goldberg <[EMAIL PROTECTED]> > Subject: [RBASE-L] - RE: SATTACH performance question > To: "RBASE-L Mailing List" <[email protected]> > Date: Tuesday, August 12, 2008, 12:05 PM > I have used both and they seem to run about the same speed. > I only use them > for querying(for now) but will be updating the sattached > tables soon!! > > Dan Goldberg > > _____ > > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of Ramsour Mike > Sent: Tuesday, August 12, 2008 8:24 AM > To: RBASE-L Mailing List > Subject: [RBASE-L] - SATTACH performance question > > > > Good morning: > > > > Is there a difference in the speed of accessing data in > foreign tables from > an SATTACHed table depending on whether the "USING > ALL" vs. "USING > <collist>" is used? > > > > i.e. Is it better to use the "USING ALL" syntax > vs. specifying exact columns > vs. not specifying any columns? > > > > Thanks for any insight. > > > > Mike Ramsour > AK Steel Coshocton Works > Quality Department > > Phone/VMS: 740-829-4340
