Here we go again

DeloitteAdmin_(Delete)_2707331

OK,When I try to unlock the ospace i have created I get an error.This is exactly what was happening to me last time, i think it is something to do with the startup scripts..The error i get is "A wrong argument type was specified"The debugger steps into the Expand method and within that method it shows an error at the Vis.replaceitem() line..Can anyone help me with this?I have not tampered with ANY other ospaces except my own, so i know it hasnt been caused by me unlocking things i shouldnt have..

David_Barker_(americ02user3_-_(deleted))

This sounds like the Builder is having a problem digesting a particular object or feature when it is unlocking the ospace. I've seen this kind of thing happen before, but usually only when attempting to inspect a feature that contains a reference to a File Handle or something of that nature.If this is the case, then you should still be able to open the module. I would then try to inspect any of the custom objects or features that I've created in the module to try to isolate the offending item and delete or modify it if I found it.If this is not the case, and you don't have too much invested in the module yet, you may want to start over again. In this case, I would highly recommend using the "Make a New Module" script that Martin Scott and I created back when V8 first came out. I believe that Donna Nalls has already mentioned that utility to you in another thread. It can provide you with a solid module base to reduce these kind of errors.Also, if you are developing and don't like to have to constantly unlock your Module every time you start your Builder, you can simply add your modules name to the changeStateOspaces = {} list located within the webbuilder.lxe file. Just make sure that the module name is fully CAPITALIZED, otherwise it won't work.e.g. function WebBuilder( \ List changeStateOspaces = {'MYMODULE'}, ...I hope this helps,David Barker