Copying an Application Help

[Smokey]

Hi

I would like to create a copy of an existing application and associated analyst library so that i can fix some errors for the new planning year. I don't want to change the existing models as it will result in deleted data when i sychronise in admin and the departments are still using the web to view last year submissions.

Can anyone advise the best solution?

My first thought was to create a new application using the existing library and call it v2 so that i would never have to sychronise the original. I tried this but got an error message at the end about not being able to create database due to file being under 128mb??

Any help

Thanks

[JaromirSeps]

I did similar thing by:
Copying the library using application tools - File - Library - Copy .. and merging everything into a single library, so you don't damage existing dlists while developing
- there should be no errors while doing this process

How did you get to the mentioned error?

Copying Oracle datastore and connecting application in Contributor,
or creating the application in Contributor as a new, recreating ATs and loading all data via Administration links (this way you get no troubles with new dlist structure)

Jaromir

[Smokey]

Thanks for the reply

I got the error when I imported back the application from deployment and tried to call it a different name. The error occurs on the create application step.

I have however fixed the problem by using a dlink to move one version summary to a new version summary within the same cube. synchronised, gtp and then broke the link zeroed all the other cubes using import macro and then made my changes in analyst to the model. My summarised version (which was all i needed)  intact.

My next problem is to find the most efficient way of creating a model when the dlist is 62000 items long but is not my elist. has any one else tried to use a hideously long dlist?