Can you take a complete screen shot of the Geodatabase Administration screen showing your versions? When you click on a version it will report the parent of the version. In order to create a child of a SPECIFIC version your mouse pointer must BE ON that version when you right-click and select new version, as pictured below. Also, what version of Arc are you using, what version of SQL, what operating system, etc...?
The "Geodatabase Administrator" was introduced at Desktop 10.1, so you wont have that as you are using Desktop 10.0.
You can check the details by right-clicking on the concerned versions in Version Manager and then checking the properties.
Thanks for your response. I attached the versions relationship. it seems to be right. Parent of Case1 is Cases
and cases' parent is Default. but as i told already, Case1 posts the changes directly to Default version instead of Cases. ( this issue is so important for me, I do not want editors who work under administrator charge be able to change geodatabase directly. )
I do not reconcile or post changed data. I am administrator ( cases version). editors do these tasks. so it is my responsibility that design database versioning in a way that Editors ( case1 version) only excess to Cases version and not to Default. it is possible that Editors (case1) delete some data or do some changes that damage database so they must not access to Default version.
Is there anybody who has already worked versioning and helps me?
The Access Level of DEFAULT version is "Protected"....so other than 'sde' user or a 'syasadmin' user, nobody else can Post edits to that version or edit in it.
So either your editor has access to credentials of the "sde" login or they have 'sysadmin' permission, which allows them to post edits to the Default. Maybe you should confirm their permissions.
If this is urgent, I'll suggest contact Tech-Support for a quick review.