When dragging and dropping Javascripts from a v5 project folder on an old server to a v7 project folder on a newer server, about half of the files cause a pop-up error dialog window stating "Cannot copy to IBFS:/Shared-Development/ProjectFolder/Change_Name.js" .

It appears that some files on the old v5 project folder are different or wrong in some way that prevents a copy to a different project folder. The target folder was new and empty prior to the attempt to copy files from the old project file. A set of .js files were selected, part of which copied and part of which flagged the error message below.

[SOLVED] Update: So based on the comments I did find a way to work around the copy issue, by not copying directly from the v5 project folder to the new v7 folder. In one case, I successfully used Windows Explorer as a source to move files into the new project folder.

This message has been edited. Last edited by: Joe Elliott,

I wouldn't do it from the Projects area of the Dev Studio Explorer window.

Are either of the two environments multi-tier, i.e. is the reporting server on a different machine than the client server? If so, the Projects area won't work.

Try copying from Environment to Environment.

Thanks for the quick reply . . . while I cannot copy from project area to project area, I can copy the files from Windows Explorer (outside of WebFOCUS software) into the new project folder with no issues. Also odd that part of the files copied, while some of them failed with the error message shown in the first post. My environment is multi-tiered with the Report server on a different platform than the Client server.

The other issue I seem to have is that I lose the connection between the forms and the Javascript regardless when I upgrade, which means I have to embed every Javascript into every form again. This means hundreds of touchpoints on the forms to re-embed all of the Javascripts into the forms where they were generated in the first place.

This message has been edited. Last edited by: Joe Elliott,