PRB: "System.NullReferenceException" Exception When You Use the DynamicProperties TableName Property in an Untyped Dataset (815118)
The information in this article applies to:
- Microsoft Visual Studio .NET (2002), Professional Edition
- Microsoft Visual Studio .NET (2002), Enterprise Architect Edition
- Microsoft Visual Studio .NET (2002), Enterprise Developer Edition
- Microsoft Visual Studio .NET (2002), Academic Edition
- Microsoft Visual Studio .NET (2003), Professional Edition
- Microsoft Visual Studio .NET (2003), Enterprise Architect Edition
- Microsoft Visual Studio .NET (2003), Enterprise Developer Edition
- Microsoft Visual Studio .NET (2003), Academic Edition
SYMPTOMSWhen you modify the TableName property of the table in a configuration file, and the table has
a relation contraint or a foreign key constraint, you may receive the System.NullReferenceException exception.CAUSEMicrosoft Visual Studio designer does not store relation information or
foreign key constraint information in the configuration file. However, when you
use the DynamicProperties node to modify the TableName property, the constraint is not changed and
the runtime continues to search for the hard-coded TableName. This behavior causes the exception.RESOLUTIONTo resolve this problem, do not use or modify
the Dynamic Properties for the TableName property while you use a relation or a foreign key
constraint. STATUS This
behavior is by design.
Modification Type: | Minor | Last Reviewed: | 7/15/2003 |
---|
Keywords: | kbConfig kberrmsg kbDevStudio kbDesigner kbprb KB815118 kbAudDeveloper |
---|
|