I'm deploying to a SQL 2000 DB and I receive the following error on 2 tables.  Cannot access property XmlSchemeNamespace.   The tables only have two or three fields.

 The table 'sys_ActiveUsers' is being prepared to be modified.
X 09/02/2007 8:44:35 PM -> Altering table 'sys_ActiveUsers' failed.
X 09/02/2007 8:44:35 PM -> FailedOperationException       
X 09/02/2007 8:44:35 PM ->  Alter failed for Table 'dbo.sys_ActiveUsers'.        
X 09/02/2007 8:44:35 PM -> UnknownPropertyException       
X 09/02/2007 8:44:35 PM ->  Cannot access property XmlSchemaNamespace.This property is not available on SQL Server 2000.       
X 09/02/2007 8:44:35 PM ->        
X 09/02/2007 8:44:35 PM -> Source     : Microsoft.SqlServer.Smo       
X 09/02/2007 8:44:35 PM ->        
X 09/02/2007 8:44:35 PM -> Stack Trace:        
X 09/02/2007 8:44:35 PM ->    at Microsoft.SqlServer.Management.Smo.SqlPropertyMetadataProvider.PropertyNameToIDLookupWithException(String propertyName, PropertyAccessPurpose pap)       
X 09/02/2007 8:44:35 PM ->    at Microsoft.SqlServer.Management.Smo.Column.ScriptAlter(StringCollection alterQuery, ScriptingOptions so)       
X 09/02/2007 8:44:35 PM ->    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.PropagateScript(StringCollection query, ScriptingOptions so, PropagateAction action)       
X 09/02/2007 8:44:35 PM ->    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.AlterImplWorker()       
X 09/02/2007 8:44:35 PM ->    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.AlterImpl()       
X 09/02/2007 8:44:35 PM ->    at Microsoft.SqlServer.Management.Smo.Table.Alter()       
X 09/02/2007 8:44:35 PM ->    at MicroFour.StrataFrame.DBEngine.SQL.DatabaseMigrator.AlterSmoObject(IAlterable ObjectToAlter, String ObjectName, DBEObjectType ObjectType)       
X 09/02/2007 8:44:35 PM ->        
• 09/02/2007 8:44:36 PM -> The table 'sys_Users' is being prepared to be modified.
• 09/02/2007 8:44:37 PM -> The table 'sys_Users' was successfully altered.
• 09/02/2007 8:44:37 PM -> The table 'sys_Licence' is being prepared to be modified.
X 09/02/2007 8:44:37 PM -> Altering table 'sys_Licence' failed.
X 09/02/2007 8:44:37 PM -> FailedOperationException       
X 09/02/2007 8:44:37 PM ->  Alter failed for Table 'dbo.sys_Licence'.        
X 09/02/2007 8:44:37 PM -> UnknownPropertyException       
X 09/02/2007 8:44:37 PM ->  Cannot access property XmlSchemaNamespace.This property is not available on SQL Server 2000.       
X 09/02/2007 8:44:37 PM ->        
X 09/02/2007 8:44:37 PM -> Source     : Microsoft.SqlServer.Smo       
X 09/02/2007 8:44:37 PM ->        
X 09/02/2007 8:44:37 PM -> Stack Trace:        
X 09/02/2007 8:44:37 PM ->    at Microsoft.SqlServer.Management.Smo.SqlPropertyMetadataProvider.PropertyNameToIDLookupWithException(String propertyName, PropertyAccessPurpose pap)       
X 09/02/2007 8:44:37 PM ->    at Microsoft.SqlServer.Management.Smo.Column.ScriptAlter(StringCollection alterQuery, ScriptingOptions so)       
X 09/02/2007 8:44:37 PM ->    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.PropagateScript(StringCollection query, ScriptingOptions so, PropagateAction action)       
X 09/02/2007 8:44:37 PM ->    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.AlterImplWorker()       
X 09/02/2007 8:44:37 PM ->    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.AlterImpl()       
X 09/02/2007 8:44:37 PM ->    at Microsoft.SqlServer.Management.Smo.Table.Alter()       
X 09/02/2007 8:44:37 PM ->    at MicroFour.StrataFrame.DBEngine.SQL.DatabaseMigrator.AlterSmoObject(IAlterable ObjectToAlter, String ObjectName, DBEObjectType ObjectType)       

Sorry, I just realized I put this under the wrong topic...

what default values do you have specified for the columns within those tables?  According to anything that I can find within Google, this is a common problem with SMO and SQL Server 2000 when people attempt to modify the DefaultConstraint on a column.

The only differences between the two tables causing the problems and the other tables in the database is that the two tables do not have auto-incremental keys. The primary key values are varchar fields and the default values are "".

When you say that the default values are "", do you mean that the textbox is blank, or that you put double quotes in them?

("")

Ah, remove that from the default value... or change it to (''), single quotes, since that's the SQL Server constant for an empty string.  You probably don't need a default value anyways since it's the primary key and you're specifying it manually anyways.

Thanks Ben, that seemed to correct my problem. I really appreciate the great support, especially when you guys are getting ready to launch a new release. 

Just one more DDT issue to resolve and I'm ready to launch...

Excellent, let's get the other one fixed, too