Visual Studio Database Pro Partial Projects Constraints Issue -

Visual Studio 2008 can use a "partial projects" in the database version so that in many projects for deploying a database Can be divided into maintenance I am looking into doing this with my project, but by pressing the following problem:

If you have a project that defines some of the base tables, and after that you have a separate project that That defines a new set of tables, DBPro seems unable to map this relationship, pointing to the tables in the first project. There is a specific error:

"There is an unresolved reference to table fu in the contract" (where Fu is in the original DB).

Another concrete example if you want to duplicate yourself for the scenario:

• Create a project called BaseDB

• Define a BDB table with the following DDL:

    create table [dbo] [user] (UserID INT identification (1,1) Primary key, Username NVRAR (20) not faucet)  

• Exporting to BDB as a partial project on your The _BaseDB.files file for the scheme

• As such, your import files have a stub reference pointing to the user table in BaseDebb.

• Define a table in DerivedDB that is called PowerUsers with DUDL:

    Table [dbo]. [PowerUsers] (PowerUserID INT identity (1,1) primary key, not UserID INT)  

• If you make a "build" at this point, then everything works.

• Add a main key control with the user from PowerUsers in the DerivDB project, following DDL:

    Optional table [dbo]. [PowerUsers] Add Control [PowerUsers_Users_FK] Foreign Key Reference (DBO). [User] (user id)  

By doing the above steps you should get permission to view the error about which I am talking.

Question:

1. Is there a way to fix barriers in database projects?

2. If not, partial projects reserved for a series of stored procedures and for the original project reserved for all base tables and DDL of barriers Should be reserved?