Bill,
One other thing to try (Bob's suggestion, where you unload the data and the schema then edit the schema, is good for a small table) is this, all from the R>: ALTER TABLE tablename ALTER COLUMN size TO xsize TEXT (8) NOCHECK Substitute your table's name for "tablename" and your new column name for "xsize" in the above. You can also unload the data and schema separately: OUTPUT tablename.dat UNLOAD DATA FOR tablename OUTPUT tablename.str UNLOAD STRUCTURE FOR tablename OUTPUT SCREEN Now edit tablename.str and change the column name. Then: DROP TABLE tablename RUN tablename.str RUN tablename.dat Needless to say, but I will anyway, back up your database before doing this. Emmitt Dove Manager, Converting Applications Development Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of Bill Owens Sent: Tuesday, December 22, 2009 2:26 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Schema Change Question Group I am using the latest release of Turbo 8 (8.0.22.31102) When I go to change a column definition, the Data Designer hangs and I have to use Task Manager to end the rbase session. The column I am changing is the only one in all of my tables.(it is defined only once in the database). The column in question comes from a converted database created in Rbase for Dos 6.1. The reason for the change is that it showed as a reserved word in Turbo8. The column name is size text (8). I make the change, click Save, get no message that the table is saved. Then I click Save and Exit and it still hangs. Then I click Close and I'm informed that there have been changes, do I want to save changes ? If I click Yes nothing happens, if I click No the Data Designer closes and there is now a locked temp table with the same number of columns and rows as the table I was attempting to change. I now have to use Task Manager to end the rbase session. I then re-open Rbase and have to delete the temp table. I then look at the table I had attempted to change the column in (see above) and the column definition changed to what I wanted when I first started. Has anyone seen this behavior and if so what was the resolution ? Thanks
