.NET Questions and Solutions

Symptoms
Consider the following scenario in Microsoft Visual Studio Team System 2008 Database Edition GDR: You have a database project that includes tables.You have another database project that includes constraints for the tables in the same solution and you add a reference to the database project that includes tables.You connect both projects to the same target database on a server.Then, you deploy the projects to the database.In this scenario, you receive a System.NullReferenceException exception and then the Visual Studio IDE crashes. If you debug this exception, you receive the following error message:

System.NullReferenceException: Object reference not set to an instance of an object.
Resolution
To resolve this problem, upgrade to Microsoft Visual Studio Team System 2008 Database Edition GDR R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970479?(http://support.microsoft.com/kb/970479/) List of fixed issues in the Microsoft Visual Studio Team System 2008 Database Edition GDR R2
Note Microsoft Visual Studio Team System 2008 Database Edition GDR R2 replaces Microsoft Visual Studio Team System 2008 Database Edition GDR.

Symptoms
When you import a Microsoft Access object from one database into anotherdatabase, any reference used by the object is not imported, and you mustre-create the reference in the target database. For example, if you insertan ActiveX control on a form, Microsoft Access automatically creates areference to the .ocx file for that control. If you then open anotherdatabase and import the form that contains the ActiveX control from thefirst database, the reference to the .ocx file is not imported with theform. This behavior also occurs when you export an object.
Resolution
A reference is not imported or exported with an object because it is notspecific to the object; instead, a reference is specific to the project ofa database.