Hi ??? There is no easy answer to this the issue goes under the name of schema evolution
esp if you need to preserve IDkeys/relationships either live with redundent property data or the only sensible way I can think of is a) export the data to some 3rd party legacy ralational product ( say MS Access) with the old shema defns b) import it into the new definition you can either do this in cache linking out via ODBC or use Access to suck from the old data and squirt to the new data with the tables as linked Cache tables via ODBC Peter On Tue, 15 Jul 2003 11:58:55 +0200, [EMAIL PROTECTED] wrote: > >Hi Florian, > >>>Is there any undocumented Intersystems tool to convert an exiting >>>global to the actual global definition? Exporting, deleting and >>>reimporting via a .gsa file doesn�t solve the problem, because the >>>reimport gives the old structure again. Same thing happens with the >>>merge command in terminal. >>> >>>Any hints to solve that problem? >> >> >> for exporting and importing data from classes you can use the SQL-Manager. >> If you don't want to do it manually, you can use the classes >> >> %SQL.Export.Mgr >> and >> %SQL.Import.Mgr > >That doesn't really solve my problem. > >Of course I can export one global with SQL, kill the global and reimport >via SQL again. But in this case I'll get new IDs as soon as there are >some records deleted in th old global. And than I have wrong references >in other dependent tables. I don't think I can export a complex tree of >classes linked to each other and reimport all that tables again with >that SQL class methods.
