Importing Readonly Routines from 7.5-->8

fridge · Post by **fridge** » 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.

ray.wurlod · Post by **ray.wurlod** » Thu Jul 03, 2008 3:53 pm

Can you change the ReadOnly setting in the export file before importing the routine?

fridge · Post by **fridge** » Thu Jul 03, 2008 6:41 pm

yeah - seems to work if u set to readonly "0" before importing - but seems if u forget and inadvertently import a readonly "1" then the routine is effectivly locked for good

a seperate channel has suggested a hacky way round this - but very hacky - still would like to know how this kind of thing is handled in the absences of version control

if the hacky way works will update but anythoughts welcome

vj_ds_dev · Post by **vj_ds_dev** » Tue Dec 02, 2008 2:02 pm

Do you have the workaround(hacky way) for this issue.