Back to the days of CUI

We are managing the users using Active directory groups for easy managability. Couple of days back one of my developer came to me complaining(come on give me a break the normal developer stuff) saying "oh man you revoked my access, I cant edit a stored procedure, I cant modify a table definition, what is going on?" I said "Dude I got tons of other stuff waiting on my mail box and you didnt mess me up too :)) why shd I revoke your access?"

He came back and with this error "Property DefaultSchema is not available for Database . This property may not exist for this object, or may not be retrievable due to insufficient access rights. (SQLEditors)"

oh gash what a hell this is? I started verifying his access rights every thing is perfect. Googlified and found out the following link. In this one of the microsoft accepts the bug in the SQL Server Management Studio, in the following conditions.

If you have users who are having logins based upon an Active Directory group.i.e they dont have access to the database directly rather, they will be part of an active directory group and that group will be having access to the database. In this case you cant specify a default schema to that group. In this case they cant use the management studio to create a table or a stored procedure.

So the solution would be use the t-sql. wow what a solution? Welcome back to the CUI world(Character user Interface).