"Essa" <essamug***@hotmail.com> wrote in message
news:532E0285-F705-4CD7-BAE2-79C18B372B24@microsoft.com...
> Hi ;
>
> I'm using the release version of SQL Server 2005 tools (Microsoft SQL
>
> Server Management Studio 9.00.1399.00) and .NET Framework 2.0
>
> (2.0.50727.42) on Windows XP SP2.
>
> My desire was to use the new tools against my existing SQL 2000 servers
>
> as well as newly installed SQL 2005 so as to only have one place to
>
> work in and access to new tool features.  This has worked great except
>
> for one issue.  When trying to modify or script some table-valued
>
> functions under Management Studio I get the following error:
>
> ===================================
>
> Property QuotedIdentifierStatus is not available for
>
> UserDefinedFunction '[dbo].[fnFunction]'. This property may not exist
>
> for this object, or may not be retrievable due to insufficient access
>
> rights.  (Microsoft.SqlServer.Smo)
>
> ===================================
>
> I can edit/script the function in the 2000 tools (Enterprise Manager
>
> and SQL Analyzer) without problem.  I can edit some table-valued
>
> functions in Management Studio but not others.  I have tried dropping
>
> the functions and re-creating them in both 2000 and 2005 tools - the
>
> create works fine in both places, but it remains
>
> un-modifiable/scriptable in the 2005 tools.
>
> Anyone else run into this problem?
>
> Additional info available for the error
>
> ===================================
>
> Program Location:
>
> at
>
> Microsoft.SqlServer.Management.Smo.PropertyCollection.HandleNullValue(Int32
>
> index)
>
> at
>
> Microsoft.SqlServer.Management.Smo.SqlSmoObject.GetPropValueOptional(String
>
> propName)
>
> at
>
> Microsoft.SqlServer.Management.Smo.SqlSmoObject.GetPropValueOptional[T](String
>
> propName, T defaultValue)
>
> at
>
> Microsoft.SqlServer.Management.Smo.ScriptNameObjectBase.CheckTextCorectness(String
>
> ddlText, Boolean enforceCreate, Boolean checkName, String[]
>
> expectedObjectTypes, DdlTextParserHeaderInfo& headerInfo)
>
> at
>
> Microsoft.SqlServer.Management.Smo.ScriptNameObjectBase.CheckAndManipulateText(String
>
> ddlText, String[] expectedObjectTypes, ScriptingOptions so, Boolean
>
> forCreate)
>
> at
>
> Microsoft.SqlServer.Management.Smo.ScriptNameObjectBase.GetTextHeader(Boolean
>
> forAlter)
>
> at
>
> Microsoft.SqlServer.Management.Smo.UserDefinedFunction.ScriptHeader(Boolean
>
> forAlter)
>
> at
>
> Microsoft.SqlServer.Management.UI.VSIntegration.Editors.VsDocumentMenuItem.ScriptExistingTextObjectToWindow(IManagedConnection
>
> mc)
>
> at
>
> Microsoft.SqlServer.Management.UI.VSIntegration.Editors.VsDocumentMenuItem.InvokeTextObject(IManagedConnection
>
> connection)
>
> at
>
> Microsoft.SqlServer.Management.UI.VSIntegration.Editors.VsDocumentMenuItem.Invoke()
>
> ===================================
>
> --
> Essa, M. Mughal
> Software Developer
> Toronto, Canada

> I'm using the release version of SQL Server 2005 tools (Microsoft SQL 
>  
> Server Management Studio 9.00.1399.00) and .NET Framework 2.0 
>  
> (2.0.50727.42) on Windows XP SP2. 
>  
> My desire was to use the new tools against my existing SQL 2000 servers
> as well as newly installed SQL 2005 so as to only have one place to 
> work in and access to new tool features.  This has worked great except 
> for one issue.  When trying to modify or script some table-valued 
> functions under Management Studio I get the following error: 
>  
>=================================== 
>  
> Property QuotedIdentifierStatus is not available for 
> UserDefinedFunction '[dbo].[fnFunction]'. This property may not exist 
> for this object, or may not be retrievable due to insufficient access 
> rights.  (Microsoft.SqlServer.Smo) 
>  
>=================================== 
>  
> I can edit/script the function in the 2000 tools (Enterprise Manager 
> and SQL Analyzer) without problem.  I can edit some table-valued 
> functions in Management Studio but not others.  I have tried dropping 
> the functions and re-creating them in both 2000 and 2005 tools - the 
> create works fine in both places, but it remains 
> un-modifiable/scriptable in the 2005 tools. 
>  
> Anyone else run into this problem? 

> Erland Sommarskog (esq***@sommarskog.se) writes:
> > Yes, this is a known bug, and it has been resolved as fixed. It only
> > affects connections to SQL 2000.
>
> I should clarify that this does not mean that the fix is publicly
> available. I only wanted to convey that Microsoft are aware of the
> issue, and the fix is to be expected to appear in SP1 for SQL 2005.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx