Eric, Try RENAME colname TO newname IN tablename
My guess is that R:Base didn't automatically make the second one a foreign key, but that in a form that includes both tables, you get the same effect, in that the form tries to link matching data from the two. I don't know of any case where R:Base creates an actual foreign key unless you explicitly tell it to in a CREATE or ALTER command, or with a checked box or menu choice in the Object Manager or RBDefine. If there really is a foreign key on the column (type LIST CONSTRAINTS FOR tablename to determine it), then DROP the constraint before you rename things and/or rebuild your table. ALTER TABLE tablename DROP CONSTRAINT constraintname Bill On Thu, 6 Dec 2001 09:19:11 -0600, Eric Peterson wrote: >I have two completely unrelated tables; one of which is not used. >Whoever created this second table mistakenly named a column matching a >column name in the first table. Rbase makes this a foreign key (which I >think is rediculous). ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l
