Eris I have been watching this thread.
It appears to me that your problem is with your database structure. In any data base there should be only one table for person type information, Name address etc. Table names like Customers, Suppliers, Prospects all have the same data wrt to names and addresses so in reality they all live in the same table. That way you do not have a problem with a customer also being a supplier as is often the case. What is important is one set of data per person, that way it is always the same be it right or wrong. As far as R:Base is concerned constraining column names to have the same data types is on of it great strengths. You want to try handling some of the professional rubbish out there on SQL server then you will appreciate the value of R:Base. Ian At 15:51 06/12/2001 -0600, Eric Peterson wrote: >Bill, thanks for you help. Found the offending table. Now I can drop >the table and create it the way I want, but I still cannot name the >columns the way I want due to Rbase. > >My problem is with Rbase's way of handling column names that are the >same. I do not want to remane any columns, I want 2 different tables to >have 2 columns to have the same name, without any relationship, or >reference, or any other such link specified or not. They are not >related, therefore I should be able to name and data type them however I >want. This is crucial to me because what people have done up to this >point is create all these rediculous, non descriptive column names. >FirstName could quite possibly be in 10 tables. So what people have >done is just add characters to the beginning. Then someone go so fed up >with trying to think about it, they didn't care what the name was (I >have a table that has 6 date columns, 2 of which are Date1, and Date2). >I want things done right this time around, and Rbase is forcing me into >bad practices. > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] >On > > Behalf Of Bill Downall > > Sent: Thursday, December 06, 2001 2:52 PM > > To: [EMAIL PROTECTED] > > Subject: RE: Duplicate Column Names = Foreign Key... UGH > > > > Eric, > > > > To find the table(s) with foreign key(s) referencing your table, you >can > > do a LIST CONSTRAINT command, and look in the column entitled > > "References" for your table name. Then look one column to the left to > > find the table name with an FK referencing your table. > > > > I would say first, RENAME the column in the other table that has a > > name you want to use in this table. Then use ALTER TABLE ... DROP > > CONSTRAINT ... to drop any FKs refering to the table on which you are > > about to perform surgery. > > > > Don't forget to look through your application files for any references >to > > the columns that you are renaming. > > > > Bill > > > > > > On Thu, 6 Dec 2001 13:59:22 -0600, Eric Peterson wrote: > > > > >I was assuming that I couldn't drop this table because I had this > > >'parlance' (that must be french for limitation). When I try to drop > > >the table the error is 'This table is referenced by a Foreign Key'. > > >Which I now found which column has a foreign key referenced > > against it, > > >but don't know what table is referencing it (how do I find this?). > > > > > >What I have is a multi level problem. I can't drop the table because > > >there's a foreign key, of which I have no idea which table is linked. > > >Secondly, I cannot just go and ALTER the table because there's > > another > > >table in the DB that contains a column name that I want to use in >this > > >table. > > > > > > > > > > > > > ================================================ > > 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 > >================================================ >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 ================================================ 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
