"Sharon Hershon" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
> Does anyone know of a way to export a project (of which there are 100's of > classes and routines) but *NOT* export the storage definitions for the > classes in 5.1? From what I can see from Tools/Export you can write it in > CDL and XML format but both include the storage definitions. Tools/Copy > Class has an option to toggle storage def's but it's only one class at a > time, and to the same namespace. Only by editing the xml files which you could automate. > Copying the storage def's is risky business when going from a Dev > environment to say, QA, where there's a large DB. Thinking about going from > QA to Production is out of the question knowing what I know about export. If you'd always copied the storage from Dev to QA to Prod then there would be no problem all versions would use the same storage map. It is also good practise to cleanup the initial development storage before transferring from Dev to QA for the first time by deleting it and then recompiling the class to create a new clean storage map. After that through Cache's storage evolution mechanism you should have no problems. HTH Herman
