G'day Eric, At 03:51 PM 06/12/2001 -0600, you 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.
In R:BASE there is absolutely no way to have FirstName = TEXT (20) in one table and FirstName = TEXT (30) in another. From a logical point of view and a naming conventions viewpoint I see much merit in this, let alone other considerations. BUT this doesn't solve your request. What about calling the columns PersonFirstName and CustFirstName to allow different lengths but also so when the poor bleep who comes along later and has to maintain the database has half a chance of knowing which way is up? >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. Hmmm... Why do you consider it a bad practice that the same column name should be the same data type? Warmest regards, Tom Grimshaw coy: Just For You Software tel: 612 9552 3311 fax: 612 9566 2164 mobile: 0414 675 903 post: PO Box 470 Glebe NSW 2037 Australia street: 3/66 Wentworth Park Rd Glebe NSW 2037 email: [EMAIL PROTECTED] web: www.just4usoftware.com.au This email and any files transmitted with it are confidential to the intended recipient and may be privileged. If you have received this email inadvertently or you are not the intended recipient, you may not disseminate, distribute, copy or in any way rely on it. Further, you should notify the sender immediately and delete the email from your computer. Whilst we have taken precautions to alert us to the presence of computer viruses, we cannot guarantee that this email and any files transmitted with it are free from such viruses. ================================================ 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
