The problem certainly sounds as if something is wrong, however to get a work 
around..... 



If the table does not have a lot of rows, simply do an unload schema and data  
from the Design menu 

for the table in question. 



RBedit the file and change the name of the column in the resulting text file. 

Input the modified text file back.  It should remove the old table and recreate 
it with 

the new column name. 



If there is a large number of rows, do a project from the original table with 
where limit = 0. 

Unload the schema for the new projected table.   Edit the file, change the 
column name 

and reload the file.   



Insert all the records from the original table into the new modified table. 

Once you confirm all the data is ok, delete the original table and rename the 
new 

table to the original name. 



-Bob 







----- Original Message ----- 
From: "Bill Owens" <[email protected]> 
To: "RBASE-L Mailing List" <[email protected]> 
Sent: Tuesday, December 22, 2009 1:25:43 PM GMT -06:00 US/Canada Central 
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 









Reply via email to