Why are my repository objects greyed out?
|Date:||8 February 2011|
|Product/Release:||Visual LANSA IDE - V12|
|Abstract:||Status of Objects in the Repository can now be easily distinguished based on their colour/highlighting|
|Submitted By:||LANSA Technical Support|
In V12 in a slave server environment, you will notice that there may be some objects in the Repository which are Greyed out. This is actually a new feature of V12.
In summary, the general rule is
Gray = Master
Black = Local
In total the following three "STATUS" of the objects may be represented.
- If an object is all black in the IDE (including task), this means that the object is stored locally and is available for editing.
- If an object is all black but task grayed out means that the object has been checked out for read-only and they grayed out task is what its locked to on the server.
- If an object is all gray means the object doesn't exist locally but is on the server only (and the task that it is locked to on the master is shown).
Taking the image above:
- File FPTAB is available locally and checked out for update. This should be available for editing.
- File HAITEST only exists on the master.
- File LZ2C has been previously checked out for read-only. Double clicking on this object would generate a not authorized message. DEE01 is the task that the object is locked to on the master system.
The main consideration is that an object in the IDE that is black except for the task has been checked out for read-only and the grayed out task is what its locked to on the master. This hold true even if you log in to the IDE with the task that the object is locked to on the master, its still in a read-only checkout state. If you then checkout the object for update, the task will now be black and the object is available for editing.