Dan,

in your command you use syntax "USING ALL".  does this table have a PRIMARY KEY 
or a UNIQUE KEY in the source data base.
 From www.rsyntax.com"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.
"

If foreign table has a PRIMARY KEY or UNIQUE KEY your syntax may interfere with 
effective communication. If the foreign table does not
have those keys can the rows be uniquely identified by a sub-set of the columns 
instead of "ALL".


If foreign table has a PRIMARY KEY or UNIQUE KEY the "USING" phrase is not 
needed. 

Jim Bentley
American Celiac Society
[email protected]
tel: 1-504-737-3293


>________________________________
>From: Dan Goldberg <[email protected]>
>To: RBASE-L Mailing List <[email protected]>
>Sent: Wednesday, August 10, 2011 1:16 PM
>Subject: [RBASE-L] - Re: SATTACH TEMPORARY
>
>
>Have you tried with V9.1? It works much better in the new version.
> 
>The temporary is to copy the data as well as the structure. So if there is 
a lot of data it could take some time. In V8 it would hang.
> 
>Dan Goldberg
> 
> 
>From: [email protected] 
>Sent: Wednesday, August 10, 2011 10:08 AM
>To: RBASE-L Mailing List 
>Subject: [RBASE-L] - SATTACH TEMPORARY
>Greetings: 
>
>Does "SATTACH TEMPORARY" only work with R:BASE tables? 
>
>I have been trying to resolve an issue 
where the SDETACH command causes intermittent grand mal crashes in R:BASE 
(Turbo 
V-8).  The "TEMPORARY" option sounded like a good approach. 
>
>Example:  SATTACH TEMPORARY `MATL_PRCSG.SCRAP_BAR_PIECE` AS `SCRAP_BAR_PIECE` 
>USING ALL 
>
>Without the 
"TEMPORARY" option the table attaches almost instantly.  With the option 
the table never attaches and R:BASE is basically locked up.  It doesn't 
crash, it just never attaches the table.  I have tried this on Oracle and 
SQL Server databases with the same result. 
>
>Am I missing something?  Any suggestions or 
comments? 
>
>Thanks for any 
input. 
>
>Mike Ramsour 
>AK Steel Coshocton Works 
>Confidentiality Notice
This message is intended exclusively for the individual or
entity to which it is addressed and may contain privileged,
proprietary, or otherwise private information.  
If you are not the named addressee, you are not authorized
to read, print, retain, copy or disseminate this message or
any part of it.  If you have received this message in error,
please notify the sender immediately by e-mail and delete
all copies of the message. 
>
>

Reply via email to