Importing Readonly Routines from 7.5-->8
Posted: Thu Jul 03, 2008 9:32 am
Hi, still having problems with some of this - this time specifically with routines.
Hit a problem with using import / export with V8 - well a few problems but will stick to this one that is easy to replicate.
Basically if a routine is exported from 7.5 to a dsx file where the routine itself is read-only and imported into V8 it is as expected created as a read-only routine.
However you cant compile it (even through Multiple-Job compile, as this now seems to screen out readonly objects).
Previously the way I would get around this is to use version control to promote the object as read/write however as VC is no more then resorted to changing the dsx file to change the Readonly "1" text to Readonly "0" and re-import.
However this approach doesnt work as cant overwrite the original readonly object.
You also cant delete/rename the routine from the project before an import as it is readonly.
You also cant hack the DS_ROUTINES UV file as an entry doesnt exist until the routine is compiled ........ can u see where I am going with this???
As an aside - tried this approach to address similar problems with Jobs - but seems the DS_JOBS readonly field nolonger links to the read/write status of the job.
Hit a problem with using import / export with V8 - well a few problems but will stick to this one that is easy to replicate.
Basically if a routine is exported from 7.5 to a dsx file where the routine itself is read-only and imported into V8 it is as expected created as a read-only routine.
However you cant compile it (even through Multiple-Job compile, as this now seems to screen out readonly objects).
Previously the way I would get around this is to use version control to promote the object as read/write however as VC is no more then resorted to changing the dsx file to change the Readonly "1" text to Readonly "0" and re-import.
However this approach doesnt work as cant overwrite the original readonly object.
You also cant delete/rename the routine from the project before an import as it is readonly.
You also cant hack the DS_ROUTINES UV file as an entry doesnt exist until the routine is compiled ........ can u see where I am going with this???
As an aside - tried this approach to address similar problems with Jobs - but seems the DS_JOBS readonly field nolonger links to the read/write status of the job.