[RBASE-L] - RE: Challenge Redefining or Adding Field toTable

[Ed Rivkin]

Bernie, Thanks for the follow-up question. I broke the data into three tables due to my forms design. I am using a two table form where the primary table is the prompt and second table is the data to be edited. It is my understanding that the Where clause in "Edit Using" is limited to the primary table. To minimize the rows presented to the user, I split the table into active, history, and "in-between". During the life of the account, the data may be edited so I have unique forms for each situation. If you have a better way to solve this, I look forward to your suggestions. Take care, Ed ec 19, 2009 08:52:27 PM, rbase-l@rbase.com wrote:  See Below: ----- Original Message ----- From: Ed Rivkin To: RBASE-L Mailing List Sent: Saturday, December 19, 2009 6:59 PM Subject: [RBASE-L] - RE: Challenge Redefining or Adding Field toTable Hi all, Thanks again for all the responses. Noodling on this a bit (shoveling 14" of snow from the walks and driveway helped me ponder) along with your responses helped solve the problem that I had created. The DB was created using 7.6; not legacy. I did an unload/reload prior to posting my first note and everything was clean in addition to the Autochk and R:Scope tried previous to the unload/reload. I have broken my DB into three segments; active, history, and a group temporarily between those two which is the reason for having the column emailg replicated a few times. Instead of having 3 different tables why not just have a column designated as  A (Active)  H (History) and T Then EMAILG would occur only in one place.  (My .02) My problem resulted from a two situations where I project a subset of the active table and am projecting the calculated field Opendyear without it's source field, Opend. Once I dropped these two tables and added Opend to my Project statements, my problem was solved. Thanks again for everyone's effort. Ed Dec 19, 2009 04:17:05 PM, rbase-l@rbase.com wrote: Razzak, I thought this would be a good time to thank you for pointing me to the importance of database maintenance over a year and a half ago when we first changed over to 7.6. I do that almost every week now and have not had errors for quite some time. It is a nice feeling to have a fresh, clean database to work with. I would urge Ed to take that advice. Have a Merry Christmas. Jim -----Original Message----- From: rbase-l@rbase.com [mailto:rbas...@rbase.com] On Behalf Of A. Razzak Memon Sent: Saturday, December 19, 2009 2:27 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Challenge Redefining or Adding Field toTable At 02:17 PM 12/19/2009, Ed Rivkin wrote: >Opendyear isn't the column I am trying to alter. It is a calculated field >that is in the table with the column that I am trying to alter. > >The column I am trying to alter is: emailg text 24 and I want to alter it >to emailg text 34. > >Regardless if I rename the other occurrences of emailg and then attempt >to change it in the remaining table OR add a new column such as: New >text 34, I get the same error messages; > -ERROR- As column OpenDYear is used in another table, its type cannot be >redefined. (2942) > -ERROR- Unable to create/modify table. (2832) Ed, It seems that you have a database structure that has been either converted or upgraded from a legacy version. Now that you are trying to modify the schema using the Data Designer of latest R:BASE versions, all data integrity rules are enforced before saving the structure. That is the reason you are seeing all those -ERROR- messages. In order to check the integrity of your database, I suggest that you do a complete UNLOAD, and then re-build the database. This single step alone should provide you with all checks and balances. During the process of re-building the entire database, you will be able to see and identify all -ERROR-s. You must correct all identified errors accordingly. Having said that, when was the last time you re-built the entire database using the UNLOAD/LOAD approach? This is the first and most important step to check the integrity of your database. The bottom line, how healthy is your database? For step-by-step instructions, you may refer to "Database Maintenance" articles specific to your version of R:BASE. From The Edge: http://www.razzak.com/fte/ You may also search for "How Healthy is Your Database?" in the archives of this R:BASE list for more tips, techniques, and discussions on this topic. Hope that helps! Very Best R:egards, Razzak.