There is no problem. "Locked" means "Locked", and not "Locked but admin can change it". As admin you can only change the config file, remove the "Locked" option, change the attribute, and put back the "Locked" option.

- Stefan 

 But it says locked on "websubmission" in the instructions for the command "Locked attributes".

Doesnt it  mean that for instance a logged in admin should be able to change a value of a submitted locked attribute.

I am looking for a possibility to have have certain attributes locked on submission but for instance admin should be able to change the data in them after they has been submitted.

No it does not mean that the admin should be able to change it afterwards. The only way is like I described it (change the config file temporarily). 

 OK!

Thank you for a fast response!

Do you plan to implement this feature in later releases?

No. 

 Is it possible in some other way to make certain attributes preset but readonly for normal user at submission but afterwards changed by admin user?

No. 

> Hi again,
> Hope I'm not draining to much time from you guys !
> 
> here is the scenario (fake one just to understand the logic..):
> My main logbook as a Option attribute Called "Electrician availables" 
> My second logbook is a list of workers and there capacities Moptions : "Electrician", "Plumber", "Genius"
> 
> So my question is:
> 
> Is it possible to load my main logbook attribute "Electrician availables" Options based on all the "Electrician" found under my second logbook ?
> 
> Thanks :)

I think that this is neither possible nor reasonable. Of course everything is possible with shell- and java-scripting, but that would be a software
package on top of ELOG.
Keep in mind we are talking about an electronic logbook here, not about a relational database.

Cheers
Andreas